From: | NikhilS <nikkhils(at)gmail(dot)com> |
---|---|
To: | "Martijn van Oosterhout" <kleptog(at)svana(dot)org> |
Cc: | "Mark Kirkwood" <markir(at)paradise(dot)net(dot)nz>, "Luke Lonergan" <llonergan(at)greenplum(dot)com>, "Raja Agrawal" <raja(dot)agrawal(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Asynchronous I/O Support |
Date: | 2006-10-20 05:43:33 |
Message-ID: | d3c4af540610192243p43fce8e4sb9d2f87b1dab703@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 10/18/06, Martijn van Oosterhout <kleptog(at)svana(dot)org> wrote:
>
> On Wed, Oct 18, 2006 at 08:04:29PM +1300, Mark Kirkwood wrote:
> > >"bgwriter doing aysncronous I/O for the dirty buffers that it is
> > >supposed to sync"
> > >Another decent use-case?
>
> Good idea, but async i/o is generally poorly supported.
Async i/o is stably supported on most *nix (apart from Linux 2.6.*) plus
Windows.
Guess it would be still worth it, since one fine day 2.6.* will start
supporting it properly too.
Regards,
Nikhils
> Is it worth considering using readv(2) instead?
>
> Err, readv allows you to split a single consecutive read into multiple
> buffers. Doesn't help at all for reads on widely areas of a file.
>
> Have a ncie day,
> --
> Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> > From each according to his ability. To each according to his ability to
> litigate.
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
>
> iD8DBQFFNhtyIB7bNG8LQkwRApNAAJ9mOhEaFqU59HRCCoJS9k9HCZZl5gCdHDWt
> FurlswevGH4CWErsjcWmwVk=
> =sQoa
> -----END PGP SIGNATURE-----
>
>
>
--
All the world's a stage, and most of us are desperately unrehearsed.
From | Date | Subject | |
---|---|---|---|
Next Message | Gurjeet Singh | 2006-10-20 05:56:48 | Re: New CRC algorithm: Slicing by 8 |
Previous Message | Dave Page | 2006-10-20 04:52:51 | Re: adminpack and pg_catalog |