From: Alexey Dobriyan <adobriyan@gmail.com>
To: David Howells <dhowells@redhat.com>
Cc: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proc: Make inline name size calculation automatic
Date: Fri, 15 Jun 2018 20:15:21 +0300 [thread overview]
Message-ID: <20180615171521.GA4417@avx2> (raw)
In-Reply-To: <15003.1529008242@warthog.procyon.org.uk>
On Thu, Jun 14, 2018 at 09:30:42PM +0100, David Howells wrote:
> Alexey Dobriyan <adobriyan@gmail.com> wrote:
>
> > > Require a minimum inline name size of 33+1 to allow for names that look
> > > like two hex numbers with a dash between.
> >
> > Why 34? /proc will fallback to separate allocation for name anyway.
>
> See above comment. I ran find on /proc and there were a bunch of files whose
> names were "<hex>-<hex>". Allow for 16-char hex addresses and add a NUL char
> to that and you get 34.
Those must be /proc/*/map_files symlinks. If that's the case,
they don't have PDEs allocated.
next prev parent reply other threads:[~2018-06-15 17:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 20:09 [PATCH] proc: Make inline name size calculation automatic Alexey Dobriyan
2018-06-14 20:30 ` David Howells
2018-06-15 17:15 ` Alexey Dobriyan [this message]
2018-06-17 21:57 ` [PATCH] proc: fixup PDE allocation bloat Alexey Dobriyan
2018-07-20 0:06 ` Shakeel Butt
2018-08-17 13:28 ` Alexey Dobriyan
-- strict thread matches above, loose matches on Subject: below --
2018-06-13 18:43 [PATCH] proc: Make inline name size calculation automatic David Howells
2018-06-19 0:42 ` Andrew Morton
2018-06-19 8:01 ` David Howells
2018-06-19 21:59 ` Andrew Morton
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=20180615171521.GA4417@avx2 \
--to=adobriyan@gmail.com \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.