[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <01000163d0e8083c-096b06d6-7202-4ce2-b41c-0f33784afcda-000000@email.amazonses.com>
Date: Tue, 5 Jun 2018 17:04:17 +0000
From: Christopher Lameter <cl@...ux.com>
To: Baoquan He <bhe@...hat.com>
cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
penberg@...nel.org, rientjes@...gle.com, iamjoonsoo.kim@....com,
akpm@...ux-foundation.org
Subject: Re: [PATCH] slab: Clean up the code comment in slab kmem_cache
struct
On Sun, 3 Jun 2018, Baoquan He wrote:
> diff --git a/include/linux/slab_def.h b/include/linux/slab_def.h
> index d9228e4d0320..3485c58cfd1c 100644
> --- a/include/linux/slab_def.h
> +++ b/include/linux/slab_def.h
> @@ -67,9 +67,10 @@ struct kmem_cache {
>
> /*
> * If debugging is enabled, then the allocator can add additional
> - * fields and/or padding to every object. size contains the total
> - * object size including these internal fields, the following two
> - * variables contain the offset to the user object and its size.
> + * fields and/or padding to every object. 'size' contains the total
> + * object size including these internal fields, while 'obj_offset'
> + * and 'object_size' contain the offset to the user object and its
> + * size.
> */
> int obj_offset;
> #endif /* CONFIG_DEBUG_SLAB */
>
Wish we had some more consistent naming. object_size and obj_offset??? And
the fields better be as close together as possible.
Acked-by: Christoph Lameter <cl@...ux.com>
Powered by blists - more mailing lists