Per Posix there's no read ordering guarantees for a file with concurrent non-exclusive readers. Use queue/locks in the application if you need ordering like this.
Regards, Andrey On Mon, Jan 11, 2010 at 7:05 PM, bank kus <kus.bank at gmail.com> wrote: > As of 2009.06 what is the policy with reordering ZFS file reads i.e., > consider the following timeline: > T0: ?Process A issues read of size 20K and gets its thread switched out > > T1: ?Process B issues reads of size 8 bytes and gets its thread switched out > > Are the 8 byte reads from B going to fall in queue _behind_ A if: > --> if A and B are from separate users? > --> If B is from the system process? > > Regards > banks > -- > This message posted from opensolaris.org > _______________________________________________ > zfs-code mailing list > zfs-code at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-code >
