o help #1 and #2
(which are likely to be cached in the app. anyway) and apps.
that want to sendfile() to the network either do horrible hacks like
lighttpd's "AIO"[2], do a read+write copy loop with AIO or don't use AIO.
[1] And allows things like IO limiting, which aio_sendfile() won't.
[2]
() to the network either do horrible hacks like
lighttpd's AIO[2], do a read+write copy loop with AIO or don't use AIO.
[1] And allows things like IO limiting, which aio_sendfile() won't.
[2] http://illiterat.livejournal.com/2989.html
--
James Antill -- [EMAIL PROTECTED]
http://www.and.org/and-httpd
"Stephen D. Williams" <[EMAIL PROTECTED]> writes:
> James Antill wrote:
> ...
> > >The
> > > time went from 3.7 to 4.4 seconds per 10.
> >
> > Ok here's a quick test that
"Stephen D. Williams" [EMAIL PROTECTED] writes:
James Antill wrote:
...
The
time went from 3.7 to 4.4 seconds per 10.
Ok here's a quick test that I've done. This passes data between 2
processes. Obv
"Stephen D. Williams" <[EMAIL PROTECTED]> writes:
> James Antill wrote:
> >
> > I seemed to miss the original post, so I can't really comment on the
> > tests. However...
>
> It was a thread in January, but just ran accross it looking for
> som
"Stephen D. Williams" [EMAIL PROTECTED] writes:
James Antill wrote:
I seemed to miss the original post, so I can't really comment on the
tests. However...
It was a thread in January, but just ran accross it looking for
something else. See below for results.
Ahh, ok.
,
> > "\177\0\0\1\3242\0\0\0\2\4\236\216\341\0\0\7\327\177\0\0"..., 28) = 28
> > <0.75>
The strace here shows select() with an infinite timeout, you're
numbers will be much better if you do (pseudo code)...
struct timeval zerotime;
zerotime.tv_sec = 0;
zerotime.t
ll_wait (include/linux/poll.h in the linux sources, with
__pollwait being in fs/select.c).
--
# James Antill -- [EMAIL PROTECTED]
:0:
* ^From: .*james@and\.org
/dev/null
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECT
"Henning P. Schmiedehausen" <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] (James Antill) writes:
>
> >"Henning P. Schmiedehausen" <[EMAIL PROTECTED]> writes:
>
> >> % telnet mail.bar.org smtp
> >> 220 mail.foo.org ESMTP read
"Henning P. Schmiedehausen" [EMAIL PROTECTED] writes:
[EMAIL PROTECTED] (James Antill) writes:
"Henning P. Schmiedehausen" [EMAIL PROTECTED] writes:
% telnet mail.bar.org smtp
220 mail.foo.org ESMTP ready
This kills loop detection. Yes,
at is pretty common is...
foo.example.com. IN A 4.4.4.4
foo.example.com. IN MX 10 mail.example.com.
foo.example.com. IN MX 20 backup-mx1.example.com.
; This is really mail.example.org.
backup-mx1.example.com. IN A 1.2.3.4
...another is to have "farms" of mail servers
timeout = hop->nextsend;
}
- poll(pfd, m, timeout - now);
+ poll(pfd, m, (timeout - now) * 1000);
/* Receive any pending ICMP errors */
for (n = 0; n < m; n++) {
--
# James Antill -- [EMAIL PR
;
}
- poll(pfd, m, timeout - now);
+ poll(pfd, m, (timeout - now) * 1000);
/* Receive any pending ICMP errors */
for (n = 0; n m; n++) {
--
# James Antill -- [EMAIL PROTECTED]
:0:
* ^From: .*[EMAIL PROTECTED]
/dev/null
-
To unsubscribe
eturn imediatley (and there might not be data) the
answer given is usually...
sigqueue( ... );
sigwaitinfo( ... );
If the above will still schedule, then Linus might be more likely to
take a patch (I'd guess that he'd look at sigtimedwait() to be like
sleep() in most other cases though).
--
James
is usually...
sigqueue( ... );
sigwaitinfo( ... );
If the above will still schedule, then Linus might be more likely to
take a patch (I'd guess that he'd look at sigtimedwait() to be like
sleep() in most other cases though).
--
James Antill -- [EMAIL PROTECTED]
"If we can't keep this sort of
15 matches
Mail list logo
