From: Andrew Morton <akpm@linux-foundation.org>
To: David Rientjes <rientjes@google.com>
Cc: Stefan Bader <stefan.bader@canonical.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-kernel@vger.kernel.org,
Eric Dumazet <eric.dumazet@gmail.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: fs/stat: Reduce memory requirements for stat_open
Date: Wed, 25 Jun 2014 15:54:43 -0700 [thread overview]
Message-ID: <20140625155443.9b0db555884e2fcc284f2842@linux-foundation.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1406251551460.4592@chino.kir.corp.google.com>
On Wed, 25 Jun 2014 15:52:30 -0700 (PDT) David Rientjes <rientjes@google.com> wrote:
> On Wed, 25 Jun 2014, Stefan Bader wrote:
>
> > Heiko and I both had the same issue. Since some x86 hardware also reaches a lot
> > of CPUs (hyperthreads included), we bumped the possible number of CPUs to 256 at
> > least for the 64bit kernel. And that resulted in failed accesses to /proc/stat
> > when memory became fragmented.
> > So the first patch will avoid this on most systems. I have not seen this myself,
> > but I would expect him to be happy with 1/2 already. For really excessive
> > hardware 2/2 will close the gap.
> > Since this is no critical bug, I am fine with 3.17, too. I have not done so,
> > yet, but I could let our reporter try the patches (again, probably not verifying
> > the second part). Just waited to do so to see whether the code settles down to
> > these changes.
> >
>
> Ok, thanks. Looks like
>
> proc-stat-convert-to-single_open_size.patch
> fs-seq_file-fallback-to-vmalloc-allocation.patch
>
> are destined for 3.17.
Actually I've bumped them into the 3.16 queue, cc stable.
next prev parent reply other threads:[~2014-06-25 22:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 13:00 Stefan Bader
2014-06-12 13:41 ` Heiko Carstens
2014-06-12 14:02 ` Stefan Bader
2014-06-24 23:44 ` David Rientjes
2014-06-25 7:04 ` Stefan Bader
2014-06-25 22:52 ` David Rientjes
2014-06-25 22:54 ` Andrew Morton [this message]
2014-07-08 13:09 ` Peter Zijlstra
2014-07-08 13:30 ` Stefan Bader
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=20140625155443.9b0db555884e2fcc284f2842@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=eric.dumazet@gmail.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
--cc=stefan.bader@canonical.com \
/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
Powered by JetHome