From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Willy Tarreau" <w@1wt.eu>,
"Марк Коренберг" <socketpair@gmail.com>,
"Tetsuo Handa" <penguin-kernel@i-love.sakura.ne.jp>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
lkp@intel.com
Subject: Re: [PATCH v4] pipe: limit the per-user amount of pages allocated in pipes
Date: Wed, 20 Jan 2016 00:11:44 +0000 [thread overview]
Message-ID: <20160120001144.GW17997@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+55aFyum2kiJNyHwT-wrFtRZC0G7qwWXPTK_dkaEme2Y3kNmA@mail.gmail.com>
On Tue, Jan 19, 2016 at 04:07:15PM -0800, Linus Torvalds wrote:
> On Mon, Jan 18, 2016 at 7:36 AM, Willy Tarreau <w@1wt.eu> wrote:
> > On no-so-small systems, it is possible for a single process to cause an
> > OOM condition by filling large pipes with data that are never read. A
> > typical process filling 4000 pipes with 1 MB of data will use 4 GB of
> > memory. On small systems it may be tricky to set the pipe max size to
> > prevent this from happening.
> >
> > This patch makes it possible to enforce a per-user soft limit above
> > which new pipes will be limited to a single page, effectively limiting
> > them to 4 kB each, as well as a hard limit above which no new pipes may
> > be created for this user. T
>
> Al, should I take this directly, or is it coming through your tree?
I'll pick it.
prev parent reply other threads:[~2016-01-20 0:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 11:06 [PATCH v3] pipe: limit the per-user amount of pages allocated in pipes Willy Tarreau
2016-01-18 12:22 ` kbuild test robot
2016-01-18 12:32 ` Willy Tarreau
2016-01-18 15:12 ` Tetsuo Handa
2016-01-18 15:29 ` Willy Tarreau
2016-01-18 15:36 ` [PATCH v4] " Willy Tarreau
2016-01-20 0:07 ` Linus Torvalds
2016-01-20 0:11 ` Al Viro [this message]
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=20160120001144.GW17997@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=socketpair@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
/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.