From: richard -rw- weinberger <richard.weinberger@gmail.com>
To: Hagen Paul Pfeifer <hagen@jauu.net>
Cc: torvalds@linux-foundation.org,
LKML <linux-kernel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Lucas De Marchi <lucas.demarchi@profusion.mobi>,
Andrew Morton <akpm@linux-foundation.org>,
jbaron@redhat.com, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH Resend] epoll: add EPOLLEXCLUSIVE support
Date: Wed, 28 Mar 2012 16:09:24 +0200 [thread overview]
Message-ID: <CAFLxGvx0m6iaDPTDkjzw6ohX6Wdmr+DgWEr_fMdyEux50JVFEw@mail.gmail.com> (raw)
In-Reply-To: <1332943060-18374-1-git-send-email-hagen@jauu.net>
On Wed, Mar 28, 2012 at 3:57 PM, Hagen Paul Pfeifer <hagen@jauu.net> wrote:
> High performance server sometimes create one listening socket (e.g. port
> 80), create a epoll file descriptor and add the socket. Afterwards
> create SC_NPROCESSORS_ONLN threads and wait for events. This often
> result in a thundering herd problem because all CPUs are scheduled.
>
> This patch add an additional flag to epoll_ctl(2) called EPOLLEXCLUSIVE.
> If a descriptor is added with this flag only one CPU is scheduled in.
>
> Signed-off-by: Hagen Paul Pfeifer <hagen@jauu.net>
> ---
> Dave rejected the patch and said not network specific. Because there
> is no epoll maintainer this time directly.
CC'ing maintainers for you...
Please use scripts/get_maintainer.pl.
--
Thanks,
//richard
next prev parent reply other threads:[~2012-03-28 14:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 13:57 [PATCH Resend] epoll: add EPOLLEXCLUSIVE support Hagen Paul Pfeifer
2012-03-28 14:09 ` richard -rw- weinberger [this message]
2012-03-28 16:21 ` Jason Baron
2012-03-28 19:58 ` Hagen Paul Pfeifer
2012-03-29 14:16 ` Jason Baron
2012-03-29 15:05 ` Hagen Paul Pfeifer
2012-03-29 15:53 ` Jason Baron
2012-03-29 16:32 ` Hagen Paul Pfeifer
2012-03-29 18:54 ` Jason Baron
2012-03-29 21:19 ` Hagen Paul Pfeifer
2012-04-05 22:30 ` Andy Lutomirski
2012-03-29 14:51 ` Hagen Paul Pfeifer
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=CAFLxGvx0m6iaDPTDkjzw6ohX6Wdmr+DgWEr_fMdyEux50JVFEw@mail.gmail.com \
--to=richard.weinberger@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hagen@jauu.net \
--cc=jbaron@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@profusion.mobi \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).