From: David Laight <David.Laight@ACULAB.COM>
To: 'Andi Kleen' <ak@linux.intel.com>, Peter Zijlstra <peterz@infradead.org>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
"Arnaldo Carvalho de Melo" <acme@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jiri Olsa <jolsa@kernel.org>,
"alexey.budankov@linux.intel.com"
<alexey.budankov@linux.intel.com>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>
Subject: RE: [PATCH 1/2] perf: Add closing sibling events' file descriptors
Date: Tue, 11 Aug 2020 14:47:03 +0000 [thread overview]
Message-ID: <9ff26c5231954e65bbd4873d54ebd727@AcuMS.aculab.com> (raw)
In-Reply-To: <20200811142955.GC1448395@tassilo.jf.intel.com>
From: Andi Kleen
> On Mon, Aug 10, 2020 at 10:36:32PM +0200, Peter Zijlstra wrote:
> > On Mon, Aug 10, 2020 at 07:45:18AM -0700, Andi Kleen wrote:
> >
> > > Unfortunately we're kind of stuck with the old NFILE=1024 default
> > > even though it makes little sense on modern servers.
> >
> > Why can't that be changed? It seems to me all of userspace changes all
> > the time; heck that system-doofus thing flushed 20+ years of sysadmin
> > experience down the drain, just cause. Why can't we up a file limit?
>
> We could try, but I believe it's hard coded in various places outside
> the kernel.
The place it really bites is select().
Although the kernel supports large bitmaps glibc doesn't.
The random bit overwrites are a PITA to debug.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2020-08-11 14:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 15:16 [PATCH 0/2] perf: Allow closing siblings' file descriptors Alexander Shishkin
2020-07-08 15:16 ` [PATCH 1/2] perf: Add closing sibling events' " Alexander Shishkin
2020-08-06 8:35 ` peterz
2020-08-06 15:32 ` Andi Kleen
2020-08-10 13:57 ` Alexander Shishkin
2020-08-10 14:45 ` Andi Kleen
2020-08-10 20:36 ` Peter Zijlstra
2020-08-11 8:12 ` Alexey Budankov
2020-08-11 14:29 ` Andi Kleen
2020-08-11 14:47 ` David Laight [this message]
2020-08-11 18:03 ` Andi Kleen
2020-08-11 21:06 ` David Laight
2020-08-11 9:47 ` Alexander Shishkin
2020-08-11 14:34 ` Andi Kleen
2020-08-11 16:21 ` Alexander Shishkin
2020-08-11 18:02 ` Andi Kleen
2020-07-08 15:16 ` [PATCH 2/2] perf record: Support closing siblings' " Alexander Shishkin
2020-07-08 21:09 ` Jiri Olsa
2020-07-16 8:42 ` [perf record] d65f0cbbc6: perf-sanity-tests.Setup_struct_perf_event_attr.fail kernel test robot
2020-07-09 8:30 ` [PATCH 0/2] perf: Allow closing siblings' file descriptors Alexey Budankov
2020-08-06 6:15 ` Adrian Hunter
2020-08-06 8:37 ` peterz
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=9ff26c5231954e65bbd4873d54ebd727@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexey.budankov@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.