public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jason Baron <jbaron@akamai.com>,
	linux-kernel@vger.kernel.org,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Salman Qazi <sqazi@google.com>, Hou Tao <houtao1@huawei.com>
Subject: Re: [PATCH] epoll: remove ep_call_nested() from ep_eventpoll_poll()
Date: Wed, 1 Nov 2017 14:07:55 -0700	[thread overview]
Message-ID: <20171101210755.yd5gerren4xosisz@linux-n805> (raw)
In-Reply-To: <20171101135354.1ffec54e1fdedcca0f2086ce@linux-foundation.org>

On Wed, 01 Nov 2017, Andrew Morton wrote:

>This is tempting, but boy it is late in the -rc cycle.
>
>How important are these workloads?  Would the world end if we held off
>on this for 4.15?

While it's very important to one customer, nested epoll is certainly not
the common case, and this performance bottleneck has been there for 7+
years, so no hurry in that regard.

I'd like to target for v4.16 some of the series of epoll patches out there
to (1) remove the remaining loop_ncalls list, and (2) remove the epmutex
global lock. So this patch would fit in fine there.

Now, could you please pick this patch up and just leave it in linux-next
for a while to get some more testing/exposure? I mainly ask because the
patch will most likely be running in production before this time.

Thanks,
Davidlohr

  reply	other threads:[~2017-11-01 21:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31  6:10 [PATCH] epoll: remove ep_call_nested() from ep_eventpoll_poll() Jason Baron
2017-10-31 14:58 ` Davidlohr Bueso
2017-11-01 20:53   ` Andrew Morton
2017-11-01 21:07     ` Davidlohr Bueso [this message]
2017-11-01 21:11       ` Davidlohr Bueso
2017-11-02  1:24     ` 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=20171101210755.yd5gerren4xosisz@linux-n805 \
    --to=dave@stgolabs.net \
    --cc=akpm@linux-foundation.org \
    --cc=houtao1@huawei.com \
    --cc=jbaron@akamai.com \
    --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