Linux Container Development
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
To: Christoph Lameter <clameter-sJ/iWh9BUns@public.gmane.org>
Cc: Linux Containers
	<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
	Paul Menage <menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Subject: Re: [RFC][PATCH 0/3] Kernel memory accounting container (v2)
Date: Mon, 17 Sep 2007 10:12:47 +0400	[thread overview]
Message-ID: <46EE1ADF.7090201@openvz.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0709141028120.15683-RYO/mD75kfhx2SFC9UQUAuF7EQX82lMiAL8bYrjMMd8@public.gmane.org>

Christoph Lameter wrote:
> On Fri, 14 Sep 2007, Pavel Emelyanov wrote:
> 
>>> Hmmmm... Okay I have seen multiple people who want to control slab 
>>> allocations and track memory for various reasons. Would it be possible to 
>>> come up with some hook that would allow a subscription to certain SLUB 
>>> events? That way multiple subsystems may track and maybe disallow certain
>>> allocations in various contexts.
>> Do you mean some more generic than just explicit call from slab_alloc, etc?
>> Ok, I will work on it.
> 
> Yes I guess an API in slub to register callbacks for these things. This 
> needs to include a way to control the granularity. Callbacks at the level 
> of slab allocations are likely not that performance critical. But some 
> uses may require control at the object level. There needs to be some way 
> to tell SLUB to disable the fast path for a particular allocated slab 
> because the API will police each individual allocation.
> 

OK. I see. I will do my best to prepare the first version this week.

Thanks,
Pavel

      parent reply	other threads:[~2007-09-17  6:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13  9:11 [RFC][PATCH 0/3] Kernel memory accounting container (v2) Pavel Emelyanov
     [not found] ` <46E8FEC7.2010707-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-09-13  9:13   ` [RFC][PATCH 1/3] Setup the kmem container Pavel Emelyanov
2007-09-13  9:14   ` [RFC][PATCH 2/3] The accounting hooks and core Pavel Emelyanov
2007-09-13  9:16   ` [RFC][PATCH 3/3] Tune caches to be accountable or not Pavel Emelyanov
2007-09-13 10:19   ` [RFC][PATCH 0/3] Kernel memory accounting container (v2) KAMEZAWA Hiroyuki
     [not found]     ` <20070913191950.ea100a62.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2007-09-13 11:33       ` Pavel Emelyanov
2007-09-13 10:46   ` Balbir Singh
     [not found]     ` <46E91520.9060701-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2007-09-13 11:28       ` Pavel Emelyanov
2007-09-13 18:36   ` Christoph Lameter
     [not found]     ` <Pine.LNX.4.64.0709131135210.9590-RYO/mD75kfhx2SFC9UQUAuF7EQX82lMiAL8bYrjMMd8@public.gmane.org>
2007-09-14  6:26       ` Pavel Emelyanov
     [not found]         ` <46EA297B.5070605-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-09-14 17:30           ` Christoph Lameter
     [not found]             ` <Pine.LNX.4.64.0709141028120.15683-RYO/mD75kfhx2SFC9UQUAuF7EQX82lMiAL8bYrjMMd8@public.gmane.org>
2007-09-17  6:12               ` Pavel Emelyanov [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=46EE1ADF.7090201@openvz.org \
    --to=xemul-gefaqzzx7r8dnm+yrofe0a@public.gmane.org \
    --cc=clameter-sJ/iWh9BUns@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    /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