Date: Wed, 22 Mar 2000 23:34:11 -0800 From: Julian Elischer <julian@elischer.org> To: Mike Smith <msmith@freebsd.org> Cc: Matthew Dillon <dillon@apollo.backplane.com>, Paul Richards <paul@originative.co.uk>, Richard Wendland <richard@netcraft.com>, Alfred Perlstein <bright@wintelcom.net>, Poul-Henning Kamp <phk@critter.freebsd.dk>, current@freebsd.org, fs@freebsd.org Subject: Re: FreeBSD random I/O performance issues Message-ID: <38D9B306.2781E494@elischer.org> References: <200003222039.MAA00661@mass.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is one of the things that made us do so badly
in the benchmarks against NT/Linux last year.
OBVIOUSLY one should be able to re-read this infoirmation
without affecting a pending write.
Mike Smith wrote:
>
> > effects of the I/O being in-progress. If a user program doesn't access
> > any of the information it recently wrote the whole mechanism winds up
> > operating asynchronously in the background. If a user program does,
> > then the write behind mechanism breaks down and you get a stall.
>
> What makes no sense is that it should be perfectly ok to _read_ this
> information back.
>
--
__--_|\ Julian Elischer
/ \ julian@elischer.org
( OZ ) World tour 2000
---> X_.---._/ presently in: Perth
v
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38D9B306.2781E494>