From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
To: Vladimir Davydov <vdavydov@parallels.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>,
Christoph Lameter <cl@linux.com>,
David Rientjes <rientjes@google.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
stable@vger.kernel.org
Subject: Re: [PATCH] slab: fix oops when reading /proc/slab_allocators
Date: Wed, 18 Jun 2014 09:31:52 +0900 [thread overview]
Message-ID: <20140618003152.GA13917@js1304-P5Q-DELUXE> (raw)
In-Reply-To: <20140617072933.GA26418@esperanza>
On Tue, Jun 17, 2014 at 11:29:33AM +0400, Vladimir Davydov wrote:
> Hi,
>
> On Tue, Jun 17, 2014 at 10:09:52AM +0900, Joonsoo Kim wrote:
> [...]
> > To fix the problem, I introduces object status buffer on each slab.
> > With this, we can track object status precisely, so slab leak detector
> > would not access active object and no kernel oops would occur.
> > Memory overhead caused by this fix is only imposed to
> > CONFIG_DEBUG_SLAB_LEAK which is mainly used for debugging, so memory
> > overhead isn't big problem.
> [...]
> >
> > +static size_t calculate_freelist_size(int nr_objs, size_t align)
> > +{
> > + size_t freelist_size;
> > +
> > + freelist_size = nr_objs * sizeof(freelist_idx_t);
> > + if (IS_ENABLED(CONFIG_DEBUG_SLAB_LEAK))
> > + freelist_size += nr_objs * sizeof(char);
> > +
> > + if (align)
> > + freelist_size = ALIGN(freelist_size, align);
> > +
> > + return freelist_size;
> > +}
> > +
> > static int calculate_nr_objs(size_t slab_size, size_t buffer_size,
> > size_t idx_size, size_t align)
> > {
> > int nr_objs;
> > + size_t remained_size;
> > size_t freelist_size;
> > + int extra_space = 0;
> >
> > + if (IS_ENABLED(CONFIG_DEBUG_SLAB_LEAK))
> > + extra_space = sizeof(char);
> > /*
> > * Ignore padding for the initial guess. The padding
> > * is at most @align-1 bytes, and @buffer_size is at
> > @@ -590,14 +641,15 @@ static int calculate_nr_objs(size_t slab_size, size_t buffer_size,
> > * into the memory allocation when taking the padding
> > * into account.
> > */
> > - nr_objs = slab_size / (buffer_size + idx_size);
> > + nr_objs = slab_size / (buffer_size + idx_size + extra_space);
>
> There is one more function that wants to know how much space per object
> is spent for management. It's calculate_slab_order():
>
> if (flags & CFLGS_OFF_SLAB) {
> /*
> * Max number of objs-per-slab for caches which
> * use off-slab slabs. Needed to avoid a possible
> * looping condition in cache_grow().
> */
> offslab_limit = size;
> offslab_limit /= sizeof(freelist_idx_t);
>
> if (num > offslab_limit)
> break;
> }
>
> May be, we should update it too?
Hello, Vladimir.
Yes, you are right! I sent v2 with this update. :)
Thanks.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-06-18 0:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 1:09 Joonsoo Kim
2014-06-17 7:29 ` Vladimir Davydov
2014-06-18 0:31 ` Joonsoo Kim [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-15 23:45 Joonsoo Kim
2014-04-16 0:01 ` Joonsoo Kim
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=20140618003152.GA13917@js1304-P5Q-DELUXE \
--to=iamjoonsoo.kim@lge.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=stable@vger.kernel.org \
--cc=vdavydov@parallels.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