Kip Macy wrote:
>
> >
> > The best fix I've thought of thus far (other than async I/O, which I
> > understand isn't ready for prime time) would be to have a number of kernel
>
> Speaking of AIO, which I would really like to use if possible, how
> actively maintained is it? The copyright on vfs_aio.c is 1997, suggesting
> to me that John Dyson has moved onto other things.
It's passively maintained. ;^)
I've become a little familiar with the code, and BDE has graciously agreed
to review whatever I do to make sure I don't hobble it. If you need help,
yell.
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters Softweyr LLC
[EMAIL PROTECTED] http://softweyr.com/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
- Re: Kernel threads Steffen Merkel
- Re: Kernel threads Kip Macy
- Re: Kernel threads Steffen Merkel
- Re: Kernel threads Richard Seaman, Jr.
- Re: Kernel threads Richard Seaman, Jr.
- Re: Kernel threads Kip Macy
- Re: Kernel threads Kip Macy
- Re: Kernel threads Mike Smith
- Re: Kernel threads Scott Hess
- AIO was Re: Kernel threads Kip Macy
- Re: AIO was Re: Kernel threads Wes Peters
- Re: AIO was Re: Kernel threads Kip Macy
- Re: AIO was Re: Kernel threads Arjan de Vet
- kernel threads Marc Tardif
- Re: kernel threads Kenneth Wayne Culver
- RE: kernel threads John Baldwin
- kernel threads Eugene L. Vorokov
- Re: kernel threads Alfred Perlstein
- RE: kernel threads John Baldwin
- Re: kernel threads Daniel Eischen
- kernel threads Renaud Molla Wanadoo

