public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Gargi Sharma <gs051095@gmail.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
	akpm@linux-foundation.org,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	keescook@chromium.org, mm-commits@vger.kernel.org,
	linux-kernel@vger.kernel.org, Rik van Riel <riel@surriel.com>
Subject: Re: + pid-delete-struct-pidmap-nr_free.patch added to -mm tree
Date: Wed, 4 Oct 2017 00:56:10 +0300	[thread overview]
Message-ID: <20171003215610.GB7023@avx2> (raw)
In-Reply-To: <CAOCi2DEwd2Q=U8WrK0GXV95aUzhiJ9iXdypvVakpjgWM7uuevQ@mail.gmail.com>

On Tue, Oct 03, 2017 at 11:09:08PM +0530, Gargi Sharma wrote:
> On Tue, Oct 3, 2017 at 9:45 PM, Oleg Nesterov <oleg@redhat.com> wrote:
> > On 10/02, Andrew Morton wrote:
> >>
> >> From: Alexey Dobriyan <adobriyan@gmail.com>
> >> Subject: pid: delete struct pidmap::nr_free
> >>
> >> There is a check in pid allocation code to skip a full page:
> >>
> >>       if (likely(atomic_read(&map->nr_free))) {
> >>               ...
> >>
> >> In practice it doesn't do anything.  To skip a pidmap page one has to have
> >> 32K consecutive pids allocated at the same time which doesn't happen.
> >>
> >> Currently the price is _every_ fork/exit on every system being slower than
> >> necessary.
> >
> > Agreed, I too never understood how can this counter help.
> >
> > Add Gargi and Rik, the next version of "Replace PID bitmap allocation with IDR
> > API" can conflict with this and the previous pid-delete-reserved_pids.patch.
> 
> I think this patch will become obsolete as pidmap will be removed. As
> for the 1/2
> patch of Alexey's series, I'll incorporate it so that rolled over PIDs
				 ^^^^^^^^^^^
> start from 1 instead of RESERVED_PIDS.

I saw IDR pids, lots of code removed indeed.

Incorporation is not really necessary as RESERVED_PIDS is an independent change.
Just send it as 2/2 or whatever the number or rebase on top of -mm.

      reply	other threads:[~2017-10-03 21:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <59d2c81b.sN3iiDcgxwFHtFRg%akpm@linux-foundation.org>
2017-10-03 16:15 ` + pid-delete-struct-pidmap-nr_free.patch added to -mm tree Oleg Nesterov
2017-10-03 17:39   ` Gargi Sharma
2017-10-03 21:56     ` Alexey Dobriyan [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=20171003215610.GB7023@avx2 \
    --to=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=gs051095@gmail.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=riel@surriel.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