From: | johnlumby <johnlumby(at)hotmail(dot)com> |
---|---|
To: | pgsql hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Extended Prefetching using Asynchronous IO - proposal and patch |
Date: | 2014-06-01 01:03:47 |
Message-ID: | BLU436-SMTP96D20E49382D359070213EA3210@phx.gbl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On 05/31/14 20:44, johnlumby wrote:
> On 05/30/14 09:36, Claudio Freire wrote:
>
> Good point. I have included the guts of your little test program
> (modified to do polling) into the existing autoconf test program
> that decides on the
> #define USE_AIO_ATOMIC_BUILTIN_COMP_SWAP.
> See config/c-library.m4.
> I hope this goes some way to answer your concern about robustness,
> as at least now if the implementation changes in some way that
> renders the polling ineffective, it will be caught in configure.
>
>
I meant to add that by including this test, which involves a fork(),
in the autoconf tester, on Windows
USE_AIO_ATOMIC_BUILTIN_COMP_SWAP would always by un-defined.
(But could then be defined manually if someone wanted to give it a try)
From | Date | Subject | |
---|---|---|---|
Next Message | Claudio Freire | 2014-06-01 05:27:11 | Re: Extended Prefetching using Asynchronous IO - proposal and patch |
Previous Message | johnlumby | 2014-06-01 00:44:28 | Re: Extended Prefetching using Asynchronous IO - proposal and patch |
From | Date | Subject | |
---|---|---|---|
Next Message | Claudio Freire | 2014-06-01 05:27:11 | Re: Extended Prefetching using Asynchronous IO - proposal and patch |
Previous Message | johnlumby | 2014-06-01 00:44:28 | Re: Extended Prefetching using Asynchronous IO - proposal and patch |