lkml.org 
[lkml]   [2008]   [Aug]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC][PATCH 1/1] cxgb3i: cxgb3 iSCSI initiator
David Miller wrote:
> From: Tom Tucker <tom@opengridcomputing.com>
> Date: Wed, 13 Aug 2008 20:26:51 -0500
>
>
>> Can you explain how this "information" somehow doesn't qualify as
>> "state". Doesn't the next expected sequence number at the very least
>> need to be updated? una? etc...?
>>
>> Could you also include the "non-state-full" information necessary to do
>> iSCSI header digest validation, data placement, and marker removal?
>>
>
> It's stateless because the full packet traverses the real networking
> stack and thus can be treated like any other packet.
>
> The data placement is a side effect that the networking stack can
> completely ignore if it chooses to.
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Ok. Maybe we're getting somewhere here ... or at least I am :-)

I'm not trying to be pedantic here but let me try and restate what I
think you said above:

- The "header" traverses the real networking stack
- The "payload" is placed either by by the hardware if possible or by
the native stack if on the exception path
- The "header" may aggregate multiple PDU (RSO)
- Data ready indications are controlled entirely by the software/real
networking stack

Thanks,
Tom



\
 
 \ /
  Last update: 2008-08-14 03:59    [from the cache]
©2003-2011 Jasper Spaans