From: Ingo Molnar <mingo@kernel.org>
To: Jason Baron <jbaron@akamai.com>
Cc: peterz@infradead.org, mingo@redhat.com, viro@zeniv.linux.org.uk,
akpm@linux-foundation.org, normalperson@yhbt.net,
davidel@xmailserver.org, mtk.manpages@gmail.com,
luto@amacapital.net, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Alexander Viro <viro@ftp.linux.org.uk>
Subject: Re: [PATCH v3 0/3] epoll: introduce round robin wakeup mode
Date: Wed, 25 Feb 2015 08:38:14 +0100 [thread overview]
Message-ID: <20150225073814.GA14558@gmail.com> (raw)
In-Reply-To: <cover.1424805740.git.jbaron@akamai.com>
* Jason Baron <jbaron@akamai.com> wrote:
> Hi,
>
> When we are sharing a wakeup source among multiple epoll
> fds, we end up with thundering herd wakeups, since there
> is currently no way to add to the wakeup source
> exclusively. This series introduces a new EPOLL_ROTATE
> flag to allow for round robin exclusive wakeups.
>
> I believe this patch series addresses the two main
> concerns that were raised in prior postings. Namely, that
> it affected code (and potentially performance) of the
> core kernel wakeup functions, even in cases where it was
> not strictly needed, and that it could lead to wakeup
> starvation (since we were are no longer waking up all
> waiters). It does so by adding an extra layer of
> indirection, whereby waiters are attached to a 'psuedo'
> epoll fd, which in turn is attached directly to the
> wakeup source.
> sched/wait: add __wake_up_rotate()
> include/linux/wait.h | 1 +
> kernel/sched/wait.c | 27 ++++++++++++++++++++++
So the scheduler bits are looking good to me in principle,
because they just add a new round-robin-rotating wakeup
variant and don't disturb the others.
Is there consensus on the epoll ABI changes? With Davide
Libenzi inactive eventpoll appears to be without a
dedicated maintainer since 2011 or so. Is there anyone who
knows the code and its usages in detail and does final ABI
decisions on eventpoll - Andrew, Al or Linus?
Thanks,
Ingo
next prev parent reply other threads:[~2015-02-25 7:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 21:25 [PATCH v3 0/3] epoll: introduce round robin wakeup mode Jason Baron
2015-02-24 21:25 ` [PATCH v3 1/3] sched/wait: add __wake_up_rotate() Jason Baron
2015-02-24 21:25 ` [PATCH v3 2/3] epoll: restrict wakeups to the overflow list Jason Baron
2015-02-24 21:25 ` [PATCH v3 3/3] epoll: Add EPOLL_ROTATE mode Jason Baron
2015-02-25 7:38 ` Ingo Molnar [this message]
2015-02-25 16:27 ` [PATCH v3 0/3] epoll: introduce round robin wakeup mode Jason Baron
2015-02-27 21:10 ` Andrew Morton
2015-02-27 21:31 ` Jonathan Corbet
2015-03-02 5:04 ` Jason Baron
2015-02-27 22:01 ` Jason Baron
2015-02-27 22:31 ` Andrew Morton
2015-03-05 0:02 ` Ingo Molnar
2015-03-05 3:53 ` Jason Baron
2015-03-05 9:15 ` Ingo Molnar
2015-03-05 20:24 ` Jason Baron
2015-03-07 12:35 ` Jason Baron
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=20150225073814.GA14558@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=jbaron@akamai.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=mtk.manpages@gmail.com \
--cc=normalperson@yhbt.net \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ftp.linux.org.uk \
--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