From: Alan Stange <stange@rentec.com>
To: Gregory Stark <stark@enterprisedb.com>
Cc: Jignesh K. Shah <J.K.Shah@Sun.COM>
Cc: Greg Smith <gsmith@gregsmith.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: 8.4 Performance improvements: was Re: Proposal of tunable fix for scalability of 8.4
Date: Fri, 13 Mar 2009 11:20:04 -0400
Message-ID: <49BA79A4.9030208@rentec.com> (raw)
In-Reply-To: <87prgl4jbh.fsf@oxford.xeocode.com>
References: <C5DDBB25.3333%scott@richrelevance.com>
<49B922C0.6050700@sun.com>
<alpine.GSO.2.01.0903121613270.1925@westnet.com>
<49BA5537.8060002@sun.com>
<87prgl4jbh.fsf@oxford.xeocode.com>
Gregory Stark wrote:
> A minute ago I said:
>
> AFAIK Opensolaris doesn't implement posix_fadvise() so there's no benefit. It
> would be great to hear if you could catch the ear of the right people to get
> an implementation committed. Depending on how the i/o scheduler system is
> written it might not even be hard -- the Linux implementation of WILLNEED is
> all of 20 lines.
>
> I noticed after sending it that that's slightly unfair. The 20-line function
> calls another function (which calls another function) to do the real readahead
> work. That function (mm/readahead.c:__do_page_cache_readahead()) is 48 lines.
>
>
It's implemented. I'm guessing it's not what you want to see though:
http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libc/port/gen/posix_fadvise.c
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: stange@rentec.com, stark@enterprisedb.com, J.K.Shah@Sun.COM, gsmith@gregsmith.com
Subject: Re: 8.4 Performance improvements: was Re: Proposal of tunable fix for scalability of 8.4
In-Reply-To: <49BA79A4.9030208@rentec.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox