All of lore.kernel.org
 help / color / mirror / Atom feed
From: Holger Brunck <holger.brunck-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
To: Peter Zijlstra <peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, "Germs,
	Frits (extern)"
	<Frits.Germs-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>,
	cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: cgroups and SCHED_IDLE
Date: Mon, 29 Jul 2013 17:54:03 +0200	[thread overview]
Message-ID: <51F6901B.4070308@keymile.com> (raw)
In-Reply-To: <20130729152529.GD22156-RM5+C6weyIYnLiPH7yDmwOa11wxjtiyuLtmvbW2Dspo@public.gmane.org>

On 07/29/2013 05:25 PM, Peter Zijlstra wrote:
> On Mon, Jul 29, 2013 at 05:14:47PM +0200, Holger Brunck wrote:
>> no, unfortunately I got the same results as before.
> 
> OK, so I'm a little confused; this works on SMP but not on UP? There's

yes this is what I see in my setup.

> lots of mention of various platforms, but since I simply don't know any
> of them its not clear if they're UP or not.
> 

as I said I have two different boards with different UPs:

arch    cpu         32/64 bit   kernel
ARM     kirkwood    32          3.10  (but 3.0 shows same problems)
powerpc MPC8247     32          3.10  (but 3.0 shows same problems)

both shows this strange behaviour.

and I have a SMP host PC (Intel(R) Core(TM)2 Quad CPU) running a 3.4 kernel
where I am unable to reproduce the problem even if I start the kernel with
maxcpus=0.

Maybe I could tomorrow have a look on another board of us which is a ppc
Quadcore. I guess this could help to increase the confusion? ;-)

Regards
Holger



  parent reply	other threads:[~2013-07-29 15:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 17:17 cgroups and SCHED_IDLE Holger Brunck
     [not found] ` <51CC7392.8080701-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
2013-07-01  8:11   ` Holger Brunck
     [not found]     ` <51D139B4.8070407-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
2013-07-23 15:56       ` Tejun Heo
     [not found]         ` <20130723155634.GD18458-9pTldWuhBndy/B6EtB590w@public.gmane.org>
2013-07-29 12:25           ` Holger Brunck
     [not found]             ` <51F65F3D.1080503-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
2013-07-29 14:07               ` Peter Zijlstra
     [not found]                 ` <20130729140723.GB22156-RM5+C6weyIYnLiPH7yDmwOa11wxjtiyuLtmvbW2Dspo@public.gmane.org>
2013-07-29 15:14                   ` Holger Brunck
     [not found]                     ` <51F686E7.6020200-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
2013-07-29 15:25                       ` Peter Zijlstra
     [not found]                         ` <20130729152529.GD22156-RM5+C6weyIYnLiPH7yDmwOa11wxjtiyuLtmvbW2Dspo@public.gmane.org>
2013-07-29 15:54                           ` Holger Brunck [this message]
     [not found]                             ` <51F6901B.4070308-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
2013-07-29 15:56                               ` Peter Zijlstra

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=51F6901B.4070308@keymile.com \
    --to=holger.brunck-skabal50j+5bdgjk7y7tuq@public.gmane.org \
    --cc=Frits.Germs-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=tj-DgEjT+Ai2ygdnm+yROfE0A@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 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.