Answer to Alex Vorona (I'm not subscribed to linux kernel list so CC me).
Serious answers to an almost troll question (no offence here :-).
1) The possibility that sendfiles blocks,
when it has to wait for disk reads / pages,
has been repeatedly mentioned (and thus known) for ages by everyb
> DS> Threads plus epoll is another.
> 20k threads and maybe more is too much :). Look at http://nginx.net/
> senction "Architecture and scalability" for example.
> DS> It really depends upon how much performance you need
> all, that hardware can take and hold :)
Why would you want 20k threads?
On Tue, 24 Apr 2007 14:33:48 +0400
Alex Vorona <[EMAIL PROTECTED]> wrote:
> Hello David,
>
> Tuesday, April 24, 2007, 1:19:49 PM, you wrote:
>
> >> sendfile function is not just a more efficient version of a read
> >> followed by a write. It reads from one fd and write to another at tha
> >> s
Hello David,
Tuesday, April 24, 2007, 1:19:49 PM, you wrote:
>> sendfile function is not just a more efficient version of a read
>> followed by a write. It reads from one fd and write to another at tha
>> same time. Please try to read 2G, and then write 2G - and how much
>> memory you will be
> David Schwartz пишет:
> > You have a misunderstanding about the semantics of 'sendfile'.
> The 'sendfile' function is just a more efficient version of a
> read followed by a write. If you did a read followed by a write,
> it would block as well (in the read).
> >
> > DS
> sendfile function i
David Schwartz пишет:
You have a misunderstanding about the semantics of 'sendfile'. The 'sendfile'
function is just a more efficient version of a read followed by a write. If you
did a read followed by a write, it would block as well (in the read).
DS
sendfile function is not just a more e
David Miller wrote:
From: voron <[EMAIL PROTECTED]>
Date: Tue, 24 Apr 2007 00:13:27 +0300
As I see, nonblocking mode is enabled - sendfile sends less than asked.
The socket is marked as non-blocking, but the disk I/O is not.
It's blocking on the disk I/O not the socket part of the o
> As I see, nonblocking mode is enabled - sendfile sends less than asked.
> But 2G via single 30 seconds sendfile call - this is blocking call. How
> can I avoid that? I prefer sendfile as fastest way to send file
> content to network socket. The problem with sendfile block on
> nonblocking
From: voron <[EMAIL PROTECTED]>
Date: Tue, 24 Apr 2007 00:13:27 +0300
> As I see, nonblocking mode is enabled - sendfile sends less than asked.
The socket is marked as non-blocking, but the disk I/O is not.
It's blocking on the disk I/O not the socket part of the operation.
-
To unsubscribe fr
Hello
I'm testing a web server nginx for films sharing in my LAN. And I've got
some interesting results. When I tried to download film or another big
file via gigabit link, I've got sendfile block with nonblocking
socket. Strace log in attach. Some commens
#enabling nonblock on fd 3
20:51:
10 matches
Mail list logo