From: David Rientjes <rientjes@google.com>
To: Stefan Bader <stefan.bader@canonical.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-kernel@vger.kernel.org,
Eric Dumazet <eric.dumazet@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: fs/stat: Reduce memory requirements for stat_open
Date: Tue, 24 Jun 2014 16:44:00 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1406241642280.22030@chino.kir.corp.google.com> (raw)
In-Reply-To: <5399B301.9030108@canonical.com>
On Thu, 12 Jun 2014, Stefan Bader wrote:
> doh, so you guys have been hit by that before. And I have missed the fact that
> single_open is special. Which makes the change for the upper limit do the wrong
> thing. While long-term it sounds like changing it to vmalloc or iterative reads
> sounds better, maybe the change from possible to online cpus might be something
> that is better acceptable as a quick fix... Not sure. At least this giving back
> a bit of attention to the matter and it is not only affecting zSeries. x86
> starts to see hw that requires a similar high possible cpus... :)
>
Heiko's patches that should fix this problem are now in -mm, so it would
be nice to know if there are any existing issues that haven't been
addressed yet with your bug report. See
http://www.ozlabs.org/~akpm/mmotm/
next prev parent reply other threads:[~2014-06-24 23:44 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 [this message]
2014-06-25 7:04 ` Stefan Bader
2014-06-25 22:52 ` David Rientjes
2014-06-25 22:54 ` Andrew Morton
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=alpine.DEB.2.02.1406241642280.22030@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=eric.dumazet@gmail.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®