Re: Good write bad read times

["Hiren Joshi" <josh@xxxxxxxxxxxxx>]

Any changes I make to the iscsi.conf files don't get used. The initiator
prefers to use these "negotiated" values. 

-----Original Message-----
From: Mike Christie [mailto:michaelc@xxxxxxxxxxx] 
Sent: 21 September 2007 17:00
To: Hiren Joshi
Cc: linux-iscsi-users@xxxxxxxxxxxxxxxxxxxxx
Subject: Re:  Good write bad read times

Hiren Joshi wrote:
> I'm sorry for the top quoting but I'm still getting used to outlook.
> 


> ************************
> Negotiated iSCSI params:
> ************************
> HeaderDigest: None
> DataDigest: None
> MaxRecvDataSegmentLength: 65536
> MaxXmitDataSegmentLength: 65536
> FirstBurstLength: 0
> MaxBurstLength: 262144
> ImmediateData: No
> InitialR2T: Yes
> MaxOutstandingR2T: 1
> 

Can you setup the target to ask for different values?

And for the initiator are you using the defaults in the iscsi.conf file
or did you change some of them? And if you changed some of them were
they reccomended by EMC/DEll or were they just numbers you were
experimenting with? The segment length values could be a little larger
and for other targets it is usefull to have FirstBurstLength set to
something larger like around MaxRecvDataSegmentLength at least and have
ImmediateData = Yes. The values you are using looking like EMC
reccomended ones though.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
linux-iscsi-users mailing list
linux-iscsi-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/linux-iscsi-users