From: Vlastimil Babka <vbabka@suse.cz>
To: David Laight <David.Laight@ACULAB.COM>,
Eric Dumazet <eric.dumazet@gmail.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
"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>,
Linux API <linux-api@vger.kernel.org>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>
Subject: Re: [PATCH v2] fs/select: add vmalloc fallback for select(2)
Date: Fri, 23 Sep 2016 11:58:34 +0200 [thread overview]
Message-ID: <3bbcc269-ec8b-12dd-e0ae-190c18bc3f47@suse.cz> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6DB0107DC8@AcuExch.aculab.com>
On 09/23/2016 11:42 AM, David Laight wrote:
> From: Vlastimil Babka
>> Sent: 22 September 2016 18:55
> ...
>> So in the case of select() it seems like the memory we need 6 bits per file
>> descriptor, multiplied by the highest possible file descriptor (nfds) as passed
>> to the syscall. According to the man page of select:
>>
>> EINVAL nfds is negative or exceeds the RLIMIT_NOFILE resource limit (see
>> getrlimit(2)).
>
> That second clause is relatively recent.
Interesting... so it was added without actually being true in the kernel
code?
>> The code actually seems to silently cap the value instead of returning EINVAL
>> though? (IIUC):
>>
>> /* max_fds can increase, so grab it once to avoid race */
>> rcu_read_lock();
>> fdt = files_fdtable(current->files);
>> max_fds = fdt->max_fds;
>> rcu_read_unlock();
>> if (n > max_fds)
>> n = max_fds;
>>
>> The default for this cap seems to be 1024 where I checked (again, IIUC, it's
>> what ulimit -n returns?). I wasn't able to change it to more than 2048, which
>> makes the bitmaps still below PAGE_SIZE.
>>
>> So if I get that right, the system admin would have to allow really large
>> RLIMIT_NOFILE to even make vmalloc() possible here. So I don't see it as a large
>> concern?
>
> 4k open files isn't that many.
> Especially for programs that are using pipes to emulate windows events.
Sure but IIUC we need 6 bits per file. That means up to almost 42k
files, we should fit into order-3 allocation, which effectively cannot
fail right now.
> I suspect that fdt->max_fds is an upper bound for the highest fd the
> process has open - not the RLIMIT_NOFILE value.
I gathered that the highest fd effectively limits the number of files,
so it's the same. I might be wrong.
> select() shouldn't be silently ignoring large values of 'n' unless
> the fd_set bits are zero.
Yeah that doesn't seem to conform to the manpage.
> Of course, select does scale well for high numbered fds
> and neither poll nor select scale well for large numbers of fds.
True.
> David
>
next prev parent reply other threads:[~2016-09-23 9:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 16:43 Vlastimil Babka
2016-09-22 16:49 ` Eric Dumazet
2016-09-22 16:56 ` Vlastimil Babka
2016-09-22 17:07 ` Eric Dumazet
2016-09-22 17:55 ` Vlastimil Babka
2016-09-23 9:42 ` David Laight
2016-09-23 9:58 ` Vlastimil Babka [this message]
2016-09-23 13:35 ` David Laight
2016-09-26 10:01 ` Vlastimil Babka
2016-09-26 15:02 ` David Laight
2016-09-27 0:01 ` Andrew Morton
2016-09-27 1:38 ` Eric Dumazet
2016-09-27 8:13 ` Vlastimil Babka
2016-09-27 13:34 ` Eric Dumazet
2016-09-27 8:06 ` Vlastimil Babka
2016-09-27 8:45 ` [PATCH v3] " Vlastimil Babka
2016-09-27 10:22 ` Michal Hocko
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=3bbcc269-ec8b-12dd-e0ae-190c18bc3f47@suse.cz \
--to=vbabka@suse.cz \
--cc=David.Laight@ACULAB.COM \
--cc=akpm@linux-foundation.org \
--cc=eric.dumazet@gmail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®