From: Vegard Nossum <vegard.nossum-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Willy Tarreau <w@1wt.eu>,
Jens Axboe <axboe-b10kYP2dOMg@public.gmane.org>
Subject: Re: [PATCH 2/2] pipe.2: document sysctls
Date: Sun, 14 Aug 2016 09:41:28 +0200 [thread overview]
Message-ID: <57B020A8.7070501@oracle.com> (raw)
In-Reply-To: <908c5c9e-f4b0-b274-e124-e5b7b505fde6-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 08/14/2016 01:13 AM, Michael Kerrisk (man-pages) wrote:
>
> Thanks. I've added this text to pipe(7) (rather than pipe(2)), and
> expanded it considerably:
Good idea!
>
> /proc files
> On Linux, the following files control how much memory can be used
> for pipes:
>
> /proc/sys/fs/pipe-max-pages (only in Linux 2.6.34)
> An upper limit, in pages, on the capacity that an unprivi‐
> leged user (one without the CAP_SYS_RESOURCE capability) can
> set for a pipe. The default value for this limit is 16
> times the default pipe capacity (see above); the lower
> limit is two pages. This interface was removed in Linux
> 2.6.35, in favor of /proc/sys/fs/pipe-max-size.
>
> /proc/sys/fs/pipe-max-size (since Linux 2.6.35)
> The maximum size (in bytes) of individual pipes created or
I think I had a mistake in my original text because this limit is not
checked at creation time (the default pipe size, PIPE_DEF_BUFFERS, is
used even when it is greater than pipe-max-size), so maybe we can take
out the "created or".
> set by users without the CAP_SYS_RESOURCE capability. The
> default value for this file is 1048576. Attempts to set a
> limit less than the page size cause write(2) to fail with
> the error EINVAL.
Maybe add in a paranthesis that 1048576 is 1 MiB?
>
> /proc/sys/fs/pipe-user-pages-hard (since Linux 4.5)
> The hard limit on the total size (in pages) of all pipes
> created or set by a single unprivileged user (i.e., one
> with neither the CAP_SYS_RESOURCE nor the CAP_SYS_ADMIN
> capability). So long as the total number of pages allo‐
> cated to pipe buffers for this user is at this limit,
> attempts to create new pipes will be denied, and attempts
> to increase a pipe's capacity will be denied.
>
> When the value of this limit is zero (which is the
> default), no hard limit is applied.
>
> /proc/sys/fs/pipe-user-pages-soft (since Linux 4.5)
> The soft limit on the total size (in pages) of all pipes
> created or set by a single unprivileged user (.e., one with
> neither the CAP_SYS_RESOURCE nor the CAP_SYS_ADMIN capabil‐
> ity). So long as the total number of pages allocated to
> pipe buffers for this user is at this limit, individual
> pipes created by a user will be limited to one page, and
> attempts to increase a pipe's capacity will be denied.
>
> When the value of this limit is zero, no soft limit is
> applied. The default value for this file is 16384, which
> permits creating up to 1024 pipes with the default capac‐
> ity.
>
> How does the above seem?
It looks great, thanks for cleaning up my measly attempt.
Vegard
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-08-14 7:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 15:35 [PATCH 1/2] pipe.2: mention fcntl and F_GETPIPE_SZ/F_SETPIPE_SZ Vegard Nossum
[not found] ` <1471016112-18025-1-git-send-email-vegard.nossum-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2016-08-12 15:35 ` [PATCH 2/2] pipe.2: document sysctls Vegard Nossum
[not found] ` <908c5c9e-f4b0-b274-e124-e5b7b505fde6@gmail.com>
[not found] ` <908c5c9e-f4b0-b274-e124-e5b7b505fde6-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-08-13 23:43 ` Michael Kerrisk (man-pages)
2016-08-14 7:41 ` Vegard Nossum [this message]
[not found] ` <57B020A8.7070501-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2016-08-14 8:04 ` Willy Tarreau
2016-08-16 21:47 ` Michael Kerrisk (man-pages)
2016-08-12 20:18 ` [PATCH 1/2] pipe.2: mention fcntl and F_GETPIPE_SZ/F_SETPIPE_SZ Michael Kerrisk (man-pages)
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=57B020A8.7070501@oracle.com \
--to=vegard.nossum-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
--cc=axboe-b10kYP2dOMg@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 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).