From: | Sean Chittenden <sean(at)chittenden(dot)org> |
---|---|
To: | Neil Conway <neilc(at)samurai(dot)com> |
Cc: | matt(at)ymogen(dot)net, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Anything to be gained from a 'Postgres Filesystem'? |
Date: | 2004-10-21 18:40:08 |
Message-ID: | A238AA78-2390-11D9-9171-000A95C705DC@chittenden.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
> As someone else noted, this doesn't belong in the filesystem (rather
> the kernel's block I/O layer/buffer cache). But I agree, an API by
> which we can tell the kernel what kind of I/O behavior to expect would
> be good.
[snip]
> The closest API to what you're describing that I'm aware of is
> posix_fadvise(). While that is technically-speaking a POSIX standard,
> it is not widely implemented (I know Linux 2.6 implements it; based on
> some quick googling, it looks like AIX does too).
Don't forget about the existence/usefulness/widely implemented
madvise(2)/posix_madvise(2) call, which can give the OS the following
hints: MADV_NORMAL, MADV_SEQUENTIAL, MADV_RANDOM, MADV_WILLNEED,
MADV_DONTNEED, and MADV_FREE. :) -sc
--
Sean Chittenden
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2004-10-21 20:28:46 | Links to OSDL test results up |
Previous Message | Josh Berkus | 2004-10-21 17:14:39 | Re: Simple machine-killing query! |