From: Davide Libenzi <davidel@xmailserver.org>
To: kuznet@ms2.inr.ac.ru
Cc: "David S. Miller" <davem@redhat.com>,
jmorris@redhat.com, jamie@shareable.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Fw: Re: [Patch][RFC] epoll and half closed TCP connections
Date: Mon, 14 Jul 2003 11:25:49 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.55.0307141122260.4828@bigblue.dev.mcafeelabs.com> (raw)
In-Reply-To: <200307141739.VAA05290@dub.inr.ac.ru>
On Mon, 14 Jul 2003 kuznet@ms2.inr.ac.ru wrote:
> > it looks as though _every_ TCP ACK you receive will cause epoll to wake up
> > a task which is interested in _any_ socket events,
>
> This is not quite true. sk->write_space() is called only after write
> queue is full, and it is exactly one wakeup until the next overflow.
>
> But, actually, yes, it is right observation: one wait queue for all
> the socket events is painful. Note, that with current poll() improvements
> are suboptimal, tcp_poll() does not know _what_ this poll polls for,
> so it has to stand in all the wait queues. The same thing kills lots
> of possible improvements.
Indeed. This can be improved though, with some serious work. The poll(2)
and epoll caller supply events he is interested in. We could have
poll_wait() (and f_op->poll()) to accept an events parameter so that the
f_op->poll() code can drop inside separate wait queue depending on what
the caller is waiting for.
- Davide
prev parent reply other threads:[~2003-07-14 18:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030713070352.3f21a9f8.davem@redhat.com>
2003-07-14 17:39 ` Fw: Re: [Patch][RFC] epoll and half closed TCP connections kuznet
2003-07-14 18:25 ` Davide Libenzi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.55.0307141122260.4828@bigblue.dev.mcafeelabs.com \
--to=davidel@xmailserver.org \
--cc=davem@redhat.com \
--cc=jamie@shareable.org \
--cc=jmorris@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).