On Tue, 2005-07-12 at 01:30 +0900, hooanon05@xxxxxxxxxxx wrote:
>
> Ming Zhang:
> > > should iet keep values for send and recv respectivey?
> > no, i would say this is not a negotiation. if iet respond a smaller
> > value to open-iscsi, then open-iscsi should use a small value base on
> > RFC.
>
> i am afraid you are misunderstanding what i wrote.
> in this case, open-iscsi declares larger size.
>
> i am wondering iet shoud tranmits the filedata splitting open-iscsi's
> MaxRecvDataSegmentLength.
> (and open-iscsi transmits the write data splitting iet's
> MaxRecvDataSegmentLength. probably open-iscsi do so.)
>
if open-iscsi ask for 128KB while a poor target respond with 32KB which
means it can not handle, open-iscsi should reduce the number to 32KB as
well since this what AND means defined in RFC.
maybe i misunderstood your question. but anyway, if IET respond 32KB,
then INI should not send anything more than 32KB. this is what i mean
negotiation.
Ming
>
> Junjiro Okajima
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
|
