mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Paul Jackson <pj@sgi.com>, Pavel Machek <pavel@ucw.cz>
Cc: kosaki.motohiro@jp.fujitsu.com,
	"Max Krasnyanskiy" <maxk@qualcomm.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Andreas Dilger <adilger@sun.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Daniel Spang <daniel.spang@gmail.com>,
	Ingo Molnar <mingo@elte.hu>,
	Jon Masters <jonathan@jonmasters.org>,
	Marcelo Tosatti <marcelo@kvack.org>,
	Paul Menage <menage@google.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Rik van Riel <riel@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Tiny cpusets -- cpusets for small systems?
Date: Mon, 25 Feb 2008 12:10:43 +0900	[thread overview]
Message-ID: <20080225120050.AE81.KOSAKI.MOTOHIRO@jp.fujitsu.com> (raw)
In-Reply-To: <20080223060911.e1d13cc1.pj@sgi.com>

Hi Pual

> Looking at some IA64 sn2 config builds I have laying about, I see the
> following text sizes for a couple of versions, showing the growth of
> the cpuset/cgroup apparatus over time:
> 
> 	25933	2.6.18-rc3-mm1/kernel/cpuset.o (Aug 2006)
> vs.
> 	37823	2.6.25-rc2-mm1/kernel/cgroup.o (Feb 2008)
> 	19558	2.6.25-rc2-mm1/kernel/cpuset.o
> 
> So the total has grown from 25933 to 57381 text bytes (note that
> this is IA64 arch; most arch's will have proportionately smaller
> text sizes.)

hm, interesting.
but unfortunately the cpuset have more than depend.(i.e. CONFIG_SMP)

To more bad thing, some embedded cpu have poor or no atomic instruction
support.
at that, turn on CONFIG_SMP become large performace regression ;)


I am not already embedded engineer.
thus, I might have made a mistake.
(BTW: I am large server engineer now)

but no thinking dependency is wrong, may be.


Pavel, what do you think it?

- kosaki



      parent reply	other threads:[~2008-02-25  3:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-23 12:09 Paul Jackson
2008-02-23 15:09 ` Paul Menage
2008-02-23 15:57   ` Paul Jackson
2008-03-12 15:01     ` Paul Mundt
2008-02-24  3:54 ` Max Krasnyansky
2008-02-26  2:05   ` Paul Jackson
2008-02-26  2:37     ` Max Krasnyanskiy
2008-02-25  3:10 ` KOSAKI Motohiro [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=20080225120050.AE81.KOSAKI.MOTOHIRO@jp.fujitsu.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=adilger@sun.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=daniel.spang@gmail.com \
    --cc=jonathan@jonmasters.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@kvack.org \
    --cc=maxk@qualcomm.com \
    --cc=menage@google.com \
    --cc=mingo@elte.hu \
    --cc=pavel@ucw.cz \
    --cc=pj@sgi.com \
    --cc=riel@redhat.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
all inboxes | Powered by JetHome®