|
Home > Archive > Perlbal > February 2005 > non-blocking disk I/O
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
non-blocking disk I/O
|
|
| christopher@baus.net 2005-02-26, 10:32 pm |
| Ok one more question. The docs for perlbal say it does non-blocking disk
I/O. I didn't think most Unix OSes, including Linux, supported
non-blocking disk I/O. Squid, for example, gets around this by using
either separate threads or processes to do disk I/O. How does perlbal
solve this?
| |
| Mark Smith 2005-02-26, 10:33 pm |
| Linux::AIO is a PERL module that lets you do asynchronous I/O by having
child processes do it.
So yes, we do it via child processes. But it's all encapsulated in the
Linux::AIO module.
On Sat, Feb 26, 2005, christopher@baus.net wrote:
> Ok one more question. The docs for perlbal say it does non-blocking disk
> I/O. I didn't think most Unix OSes, including Linux, supported
> non-blocking disk I/O. Squid, for example, gets around this by using
> either separate threads or processes to do disk I/O. How does perlbal
> solve this?
--
Mark Smith
junior@danga.com
| |
| christopher@baus.net 2005-02-26, 10:48 pm |
|
> Linux::AIO is a PERL module that lets you do asynchronous I/O by having
> child processes do it.
>
> So yes, we do it via child processes. But it's all encapsulated in the
> Linux::AIO module.
>
Ah I see. I'm not a PERL programmer myself.
Thanks for the info by the way. I've written my own proxy in C++ that is
very similar to perlbal although my focus is a bit different. I was just
seeing what ideas I could glean from your experience perlbal.
Christopher
|
|
|
|
|