From: Jason Baron <jbaron@akamai.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
Salman Qazi <sqazi@google.com>
Subject: Re: [PATCH] epoll: avoid calling ep_call_nested() from ep_poll_safewake()
Date: Tue, 31 Oct 2017 10:14:47 -0400 [thread overview]
Message-ID: <2a96ebdd-f24b-23f3-2e53-d04a717c4378@akamai.com> (raw)
In-Reply-To: <20171028140533.e3n4zpno66kyfdm3@linux-n805>
On 10/28/2017 10:05 AM, Davidlohr Bueso wrote:
> On Wed, 18 Oct 2017, Jason Baron wrote:
>
>> http://lkml.iu.edu/hypermail//linux/kernel/1501.1/05905.html
>>
>> We can work through these ideas or others...
>
> So, unsurprisingly, I got some _really_ good results on the epoll_wait()
> benchmark by removing the readywalk list altogether -- something like
> 4000% in some cases. It's also survived more testing, although I'm still
> waiting for customer confirmation on his real workload, which helps
> further test the changes (along with this patch to move the safewake
> list to debug).
>
> Could you please resend patch 1 in the series above?
>
Hi,
I've resent patch 1 with some cleanups now. Thanks for the testing feedback.
Thanks,
-Jason
next prev parent reply other threads:[~2017-10-31 14:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 18:48 [PATCH] epoll: avoid calling ep_call_nested() from ep_poll_safewake() Jason Baron
2017-10-17 15:37 ` Davidlohr Bueso
2017-10-18 14:03 ` Jason Baron
2017-10-28 14:05 ` Davidlohr Bueso
2017-10-31 14:14 ` Jason Baron [this message]
2018-01-18 11:00 ` Hou Tao
2018-01-18 21:18 ` 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=2a96ebdd-f24b-23f3-2e53-d04a717c4378@akamai.com \
--to=jbaron@akamai.com \
--cc=akpm@linux-foundation.org \
--cc=dave@stgolabs.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sqazi@google.com \
--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 NNTP newsgroup(s).