linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Nicholas Piggin' <npiggin@gmail.com>, Vlastimil Babka <vbabka@suse.cz>
Cc: Jason Baron <jbaron@akamai.com>,
	Hillf Danton <hillf.zj@alibaba-inc.com>,
	'Alexander Viro' <viro@zeniv.linux.org.uk>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	'Michal Hocko' <mhocko@kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Eric Dumazet <eric.dumazet@gmail.com>
Subject: RE: [PATCH] fs/select: add vmalloc fallback for select(2)
Date: Tue, 27 Sep 2016 11:37:24 +0000	[thread overview]
Message-ID: <063D6719AE5E284EB5DD2968C1650D6DB010A97D@AcuExch.aculab.com> (raw)
In-Reply-To: <20160927212458.3ab42b41@roar.ozlabs.ibm.com>

From: Nicholas Piggin
> Sent: 27 September 2016 12:25
> On Tue, 27 Sep 2016 10:44:04 +0200
> Vlastimil Babka <vbabka@suse.cz> wrote:
> 
> > On 09/23/2016 06:47 PM, Jason Baron wrote:
> > > Hi,
> > >
> > > On 09/23/2016 03:24 AM, Nicholas Piggin wrote:
> > >> On Fri, 23 Sep 2016 14:42:53 +0800
> > >> "Hillf Danton" <hillf.zj@alibaba-inc.com> wrote:
> > >>
> > >>>>
> > >>>> The select(2) syscall performs a kmalloc(size, GFP_KERNEL) where size grows
> > >>>> with the number of fds passed. We had a customer report page allocation
> > >>>> failures of order-4 for this allocation. This is a costly order, so it might
> > >>>> easily fail, as the VM expects such allocation to have a lower-order fallback.
> > >>>>
> > >>>> Such trivial fallback is vmalloc(), as the memory doesn't have to be
> > >>>> physically contiguous. Also the allocation is temporary for the duration of the
> > >>>> syscall, so it's unlikely to stress vmalloc too much.
> > >>>>
> > >>>> Note that the poll(2) syscall seems to use a linked list of order-0 pages, so
> > >>>> it doesn't need this kind of fallback.
> > >>
> > >> How about something like this? (untested)
> >
> > This pushes the limit further, but might just delay the problem. Could be an
> > optimization on top if there's enough interest, though.
> 
> What's your customer doing with those selects? If they care at all about
> performance, I doubt they want select to attempt order-4 allocations, fail,
> then use vmalloc :)

If they care about performance they shouldn't be passing select() lists that
are anywhere near that large.
If the number of actual fd is small - use poll().

Otherwise you want one of the 'event' mechanisms in order to avoid setting
the markers on every fd after every event (can't remember how you do that
in Linux).

At least this isn't SYSV - poll() was O(n^2) in the number of fd
(because the fd were on a linked list).

	David

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2016-09-27 11:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22 15:28 Vlastimil Babka
2016-09-22 16:24 ` Eric Dumazet
2016-09-22 16:40   ` Vlastimil Babka
2016-09-23  6:42 ` Hillf Danton
2016-09-23  7:24   ` Nicholas Piggin
2016-09-23 16:47     ` Jason Baron
2016-09-27  8:44       ` Vlastimil Babka
2016-09-27 11:24         ` Nicholas Piggin
2016-09-27 11:37           ` David Laight [this message]
2016-09-27 11:42             ` Nicholas Piggin
2016-09-27 11:51               ` Vlastimil Babka
2016-09-28 16:30                 ` David Laight
2016-09-28 20:04                   ` Vlastimil Babka

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=063D6719AE5E284EB5DD2968C1650D6DB010A97D@AcuExch.aculab.com \
    --to=david.laight@aculab.com \
    --cc=eric.dumazet@gmail.com \
    --cc=hillf.zj@alibaba-inc.com \
    --cc=jbaron@akamai.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=npiggin@gmail.com \
    --cc=vbabka@suse.cz \
    --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