From: Mike C. <mi...@us...> - 2005-04-11 19:03:12
|
Firggin hate bugtracker - no threading, and I seem to reply to myself a lot. SourceForge.net wrote: > Bugs item #1180968, was opened at 2005-04-11 11:57 > Message generated for change (Comment added) made by nobody > You can respond by visiting: > https://sourceforge.net/tracker/?func=detail&atid=387023&aid=1180968&group_id=26396 > > Category: iscsi-drvr > Group: 4.0.2 > Status: Open > Resolution: None > Priority: 5 > Submitted By: Dave Wysochanski (wysochanski) > Assigned to: Manish Kumar Bhojasia (bhojas) > Summary: max_recv_data_segment_len should be per target and initiator > > Initial Comment: > The max_recv_data_segment_len is a declared value in the > login. Thus, the initiator can have a different value > than the > target. The iscsi transport class should show each value > (right now it only shows the initiator). > > This was found on the latest 4-0 branch but applies to > 4.0.2 tarball. > > ---------------------------------------------------------------------- > > Comment By: Nobody/Anonymous (nobody) > Date: 2005-04-11 11:59 > > Message: > Logged In: NO > > smitha has a patch for this. did you send it upstream? > I remember this better now. I think we could not come up with the proper names that all the initiators were using. we do send/recv. some do tgt/init. > ---------------------------------------------------------------------- > > You can respond by visiting: > https://sourceforge.net/tracker/?func=detail&atid=387023&aid=1180968&group_id=26396 > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > linux-iscsi-devel mailing list > lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-iscsi-devel > |