linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Davydov <vdavydov@parallels.com>
To: Christoph Lameter <cl@linux.com>
Cc: hannes@cmpxchg.org, mhocko@suse.cz, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH RFC 3/3] slub: reparent memcg caches' slabs on memcg offline
Date: Thu, 22 May 2014 17:47:28 +0400	[thread overview]
Message-ID: <20140522134726.GA3147@esperanza> (raw)
In-Reply-To: <alpine.DEB.2.10.1405211912400.4433@gentwo.org>

On Wed, May 21, 2014 at 07:13:21PM -0500, Christoph Lameter wrote:
> On Wed, 21 May 2014, Vladimir Davydov wrote:
> 
> > Do I understand you correctly that the following change looks OK to you?
> 
> Almost. Preemption needs to be enabled before functions that invoke the
> page allocator etc etc.

I need to disable preemption only in slab_free, which never blocks
according to its semantics, so everything should be fine just like that.

--
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>

  reply	other threads:[~2014-05-22 13:47 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 13:48 [PATCH RFC 0/3] kmemcg slab reparenting Vladimir Davydov
2014-05-13 13:48 ` [PATCH RFC 1/3] slub: keep full slabs on list for per memcg caches Vladimir Davydov
2014-05-14 16:16   ` Christoph Lameter
2014-05-15  6:34     ` Vladimir Davydov
2014-05-15 15:15       ` Christoph Lameter
2014-05-16 13:06         ` Vladimir Davydov
2014-05-16 15:05           ` Christoph Lameter
2014-05-13 13:48 ` [PATCH RFC 2/3] percpu-refcount: allow to get dead reference Vladimir Davydov
2014-05-13 13:48 ` [PATCH RFC 3/3] slub: reparent memcg caches' slabs on memcg offline Vladimir Davydov
2014-05-14 16:20   ` Christoph Lameter
2014-05-15  7:16     ` Vladimir Davydov
2014-05-15 15:16       ` Christoph Lameter
2014-05-16 13:22         ` Vladimir Davydov
2014-05-16 15:03           ` Christoph Lameter
2014-05-19 15:24             ` Vladimir Davydov
2014-05-19 16:03               ` Christoph Lameter
2014-05-19 18:27                 ` Vladimir Davydov
2014-05-21 13:58                   ` Vladimir Davydov
2014-05-21 14:45                     ` Christoph Lameter
2014-05-21 15:14                       ` Vladimir Davydov
2014-05-22  0:15                         ` Christoph Lameter
2014-05-22 14:07                           ` Vladimir Davydov
2014-05-21 14:41                   ` Christoph Lameter
2014-05-21 15:04                     ` Vladimir Davydov
2014-05-22  0:13                       ` Christoph Lameter
2014-05-22 13:47                         ` Vladimir Davydov [this message]
2014-05-22 19:25                           ` Christoph Lameter
2014-05-23 15:26                             ` Vladimir Davydov
2014-05-23 17:45                               ` Christoph Lameter
2014-05-23 19:57                                 ` Vladimir Davydov
2014-05-27 14:38                                   ` Christoph Lameter

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=20140522134726.GA3147@esperanza \
    --to=vdavydov@parallels.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    /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;
as well as URLs for NNTP newsgroup(s).