[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1506344991.21121.78.camel@surriel.com>
Date: Mon, 25 Sep 2017 09:09:51 -0400
From: Rik van Riel <riel@...riel.com>
To: Gargi Sharma <gs051095@...il.com>, linux-kernel@...r.kernel.org
Cc: julia.lawall@...6.fr, akpm@...ux-foundation.org, mingo@...nel.org,
pasha.tatashin@...cle.com, ktkhai@...tuozzo.com, oleg@...hat.com
Subject: Re: [PATCH 1/4] pid: Replace pid bitmap implementation with IDR API
On Mon, 2017-09-25 at 08:56 -0400, Gargi Sharma wrote:
> This patch replaces the current bitmap implemetation for
> Process ID allocation. Functions that are no longer required,
> for example, free_pidmap(), alloc_pidmap(), etc. are removed.
> The rest of the functions are modified to use the IDR API.
> The change was made to make the PID allocation less complex by
> replacing custom code with calls to generic API.
Nice work, Gargi!
> Signed-off-by: Gargi Sharma <gs051095@...il.com>
> --- a/arch/powerpc/platforms/cell/spufs/sched.c
> +++ b/arch/powerpc/platforms/cell/spufs/sched.c
> @@ -1093,7 +1093,7 @@ static int show_spu_loadavg(struct seq_file *s,
> void *private)
> LOAD_INT(c), LOAD_FRAC(c),
> count_active_contexts(),
> atomic_read(&nr_spu_contexts),
> - task_active_pid_ns(current)->last_pid);
> + task_active_pid_ns(current)->idr.idr_next-1);
> return 0;
> }
The repeated use of "idr.idr_next - 1" suggests that maybe this could
be hidden behind a new IDR API, but that could be something for a
follow-up patch.
There already is the idr_get_cursor function, but you would still
have to subtract 1 from the value returned by idr_get_cursor...
Other than that nitpick, this patch looks good to me.
Reviewed-by: Rik van Riel <riel@...hat.com>
kind regards,
Rik van Riel
--
All Rights Reversed.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists