From: David Laight <David.Laight@ACULAB.COM>
To: 'Vlastimil Babka' <vbabka@suse.cz>,
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 13:35:52 +0000 [thread overview]
Message-ID: <063D6719AE5E284EB5DD2968C1650D6DB0107FEB@AcuExch.aculab.com> (raw)
In-Reply-To: <3bbcc269-ec8b-12dd-e0ae-190c18bc3f47@suse.cz>
From: Vlastimil Babka
> Sent: 23 September 2016 10:59
...
> > 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.
An application can reduce RLIMIT_NOFILE below that of an open file.
David
next prev parent reply other threads:[~2016-09-23 13:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 16:43 [PATCH v2] fs/select: add vmalloc fallback for select(2) 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
2016-09-23 13:35 ` David Laight [this message]
2016-09-26 10:01 ` Vlastimil Babka
2016-09-26 15:02 ` David Laight
2016-09-25 18:50 ` Andi Kleen
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=063D6719AE5E284EB5DD2968C1650D6DB0107FEB@AcuExch.aculab.com \
--to=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=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;
as well as URLs for NNTP newsgroup(s).