[lkml]   [2008]   [Aug]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [RFC][PATCH 1/1] cxgb3i: cxgb3 iSCSI initiator
    David Miller wrote:
    > From: Tom Tucker <>
    > 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.
    How do you envision programming such a device? It will need TCP and
    iSCSI state to have any chance of doing useful and productive placement
    of data. The smarts about the iSCSI stateless offload hw will be in the
    device driver, probably the iscsi device driver. How will it gather the
    information from the TCP stack to insert the correct state for a flow
    into the hw cache?

     \ /
      Last update: 2008-08-14 03:55    [W:0.021 / U:4.356 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site