-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of 'Alfred Perlstein'
Sent: Tuesday, May 01, 2001 8:36 AM
To: Charles Randall
Cc: �L�^�W; Freebsd-Hackers
Subject: Re: write() vs aio_write()
* Charles Randall <[EMAIL PROTECTED]> [010430 10:26] wrote:
> Regarding aio_*, Alfred Perlstein writes:
> >It's a good idea to use it for disk IO, probably not a good
> >idea for network IO.
>
> Could you elaborate?
Sure.
Network IO can be done without blocking (unless you take a fault
on the source address of your data). Hence the additional context
switching required by aio is not needed.
Disk IO probably stands a good chance of blocking your application,
if you can offload that blocking to a kernel thread you should be
able to continue serving content.
By the way.....
I think synchonous I/O include blocking and non-blocking I/O
and asynchonous I/O is non-blocking I/O, but it is signal-driven.........
Am I right ????
--
-Alfred Perlstein - [[EMAIL PROTECTED]]
Instead of asking why a piece of software is using "1970s technology,"
start asking why software is ignoring 30 years of accumulated wisdom.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
