RE: iSCSI: need for new data SNACK code?

["Randy Jennings" <randyj@data-transit.com>]

> > The flag per task is not needed - I'd expect the Target to look
> > at the Data PDUs it would have to resend, check them against the max
> > Data PDU size for this connection and fail the regular SNACK if any
> > PDU is too large
>
> I am afraid there's no free lunch here.  In this description, you're now
> expecting targets to maintain the PDU size of every PDU that it shipped
> for each of the tasks, which causes a metadata explosion.  This
> was discussed
> by Eddy Quicksall and myself in an earlier thread - "changing
> MaxPDUDataLength".

I did not check the thread, but I remember your conversation with Eddy
Quicksall.

However, I do not remember what was said about knowing the length of the
PDU.  From this isolated discussion, though, it seems like you would at
least be able to recalculate the length of the PDU at all times or you could
never send it again.  (Unless you redid all the steps that got to that point
in the first place, and I do not think that is possible based off a PDU id
number...)

Am I missing something?

Sincerely,
Randy
Data Transit