|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: iscsi: unsolicited data questionDennis,
The target can tell
from the command whether there will be unsolicited data or not. bit 0 of the
Flags and Task Attributes field ( the F bit) in the SCSI Command PDU is 1
if there are no unsolicited Data-Out PDUs. Also, if there is unsolicited data,
the amount of unsolicited data sent is the lesser of the data transfer length or
FirstBurstSize so if bit 0 indicates unsolicited data will be sent, the target
knows where its first R2T will start.
Pat
-----Original Message-----
From: Dennis Young [mailto:dyoung@rhapsodynetworks.com] Sent: Wednesday, June 12, 2002 10:05 AM To: 'Julian Satran' Cc: ips@ece.cmu.edu; owner-ips@ece.cmu.edu Subject: RE: iscsi: unsolicited data question Julian,
This
leads me to a more interesting question.
A session with InitialR2T=No in effect, i.e. unsolicited
Data-out
allowed, could cause unintended waste of bandwidth, depending
on
how
fast the target sends our R2T in response to the SCSI Write.
If the
target sees the unsolicited Data-out PDU before building the
R2T,
then everything is fine.
If the
target doesn't see the unsolicited Data-out PDU before
building
the
R2T, the R2T would request the same portion of data in the
unsolicited Data-out, thus bandwidth is wasted.
The
question is, how can a target be smart about this?
Should
the target wait a moment for the possible
unsolicited Data-out
after
receiving each SCSI Write, this sounds kludgy.
Also,
why do we need the unsolicited Data-out PDU feature when
there
is ImmediateData?
Regards,
Dennis
Home Last updated: Wed Jun 12 16:18:40 2002 10712 messages in chronological order |