[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANQeFDBGzxF0r-+dxp5jcRnOCe8NgEzRgmc-84bGRBqiYg5KhA@mail.gmail.com>
Date: Tue, 29 May 2018 09:48:20 +0800
From: Liu Bo <obuil.liubo@...il.com>
To: Kent Overstreet <kent.overstreet@...il.com>
Cc: linux-kernel@...r.kernel.org, viro@...iv.linux.org.uk,
akpm@...ux-foundation.org, willy@...radead.org,
gregkh@...uxfoundation.org, linux-security-module@...r.kernel.org,
selinux@...ho.nsa.gov, dev@...nvswitch.org, shli@...nel.org,
linux-raid@...r.kernel.org
Subject: Re: [PATCH 1/6] Generic radix trees
On Sat, May 26, 2018 at 1:56 PM, Kent Overstreet
<kent.overstreet@...il.com> wrote:
> On Sat, May 26, 2018 at 11:16:42AM +0800, Liu Bo wrote:
>> > +/*
>> > + * Returns pointer to the specified byte @offset within @radix, allocating it if
>> > + * necessary - newly allocated slots are always zeroed out:
>> > + */
>> > +void *__genradix_ptr_alloc(struct __genradix *radix, size_t offset,
>> > + gfp_t gfp_mask)
>> > +{
>> > + struct genradix_node **n;
>>
>> Any reason that " struct genradix_node ** " is used here instead of "
>> struct genradix_node * "?
>>
>> Looks like this function only manipulates *n, am I missing something?
>
> It stores to *n, when it has to allocate a node (including the root)
I see, thanks for the explanation.
thanks,
liubo
Powered by blists - more mailing lists