The iSCSI protocol has a "max_cmd_sn" parameter passed in each iscsi response. It sets a window size for the initiator indicating the number of commands it is allowed to send to the target.
Dan > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Grant Grundler > Sent: Wednesday, September 21, 2005 6:22 AM > To: Roland Dreier > Cc: Vu Pham; openib-general > Subject: Re: [openib-general][PATCH][SRP] bug fixes & fmr supported, > > On Tue, Sep 20, 2005 at 04:52:54PM -0700, Roland Dreier wrote: > ... > > I think it makes more sense to handle this the same way I handled > > max_sectors: make it a per-target parameter passed in when > connecting > > to the target. We could make cmds_per_lun a similar parameter, but > > are there likely to be any SRP targets that need this to be limited? > > Probably. At least it is necessary for regular SCSI devices. > This is normally how one can enforce "fairness" by preventing > o one (or more) initiator from monopolizing a shared the target device > o one LUN from saturating the link (and thus access to other LUNS). > > There might be other (better?) mechanisms for iSCSI/IB to handle > these situations. Limiting the number of pending requests is > known to work on previous technologies. > > hth, > grant > _______________________________________________ > openib-general mailing list > [email protected] > http://openib.org/mailman/listinfo/openib-general > > To unsubscribe, please visit > http://openib.org/mailman/listinfo/openib-general > _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
