All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Christoph Lameter <cl@gentwo.org>, Tejun Heo <htejun@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@redhat.com>, Matt Mackall <mpm@selenic.com>,
	Gilad Ben-Yossef <gilad@benyossef.com>, Jens Axboe <axboe@fb.com>,
	Pekka Enberg <penberg@kernel.org>,
	David Rientjes <rientjes@google.com>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: kernel: smp: WARNING at kernel/smp.c:673
Date: Mon, 04 Aug 2014 14:41:30 -0400	[thread overview]
Message-ID: <53DFD3DA.4060302@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1408041100240.9968@gentwo.org>

On 08/04/2014 12:00 PM, Christoph Lameter wrote:
> On Mon, 4 Aug 2014, Tejun Heo wrote:
> 
>>> Yuck. I meant cgroup code. There were some patches that were suggesting a
>>> shrink operation when taking down a cgroup. Does that also apply to per
>>> cpu downing?
>>
>> Heh, I have no idea what you're talking about.  cgroup currently
>> doesn't do anything like that.  It doesn't even make use of the cpu
>> hotplug hooks.
> 
> Something is running a kmem_cache_shrink from cpu down hooks. Thats weird.
> 

That's not cpu down, that's mem down.


Thanks,
Sasha

      reply	other threads:[~2014-08-04 18:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04  2:57 kernel: smp: WARNING at kernel/smp.c:673 Sasha Levin
2014-08-04  6:48 ` Joonsoo Kim
2014-08-04 10:49   ` Gilad Ben-Yossef
2014-08-04 21:23   ` Andrew Morton
2014-08-04 15:00 ` Christoph Lameter
2014-08-04 15:03   ` Tejun Heo
2014-08-04 15:21     ` Christoph Lameter
2014-08-04 15:22       ` Tejun Heo
2014-08-04 16:00         ` Christoph Lameter
2014-08-04 18:41           ` Sasha Levin [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=53DFD3DA.4060302@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@fb.com \
    --cc=cl@gentwo.org \
    --cc=davej@redhat.com \
    --cc=gilad@benyossef.com \
    --cc=htejun@gmail.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.