public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: "Paul Menage" <menage@google.com>
Cc: kosaki.motohiro@jp.fujitsu.com, maxk@qualcomm.com,
	alan@lxorguk.ukuu.org.uk, adilger@sun.com,
	akpm@linux-foundation.org, daniel.spang@gmail.com, mingo@elte.hu,
	jonathan@jonmasters.org, marcelo@kvack.org, pavel@ucw.cz,
	a.p.zijlstra@chello.nl, riel@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: Tiny cpusets -- cpusets for small systems?
Date: Sat, 23 Feb 2008 09:57:52 -0600	[thread overview]
Message-ID: <20080223095752.25c1ba28.pj@sgi.com> (raw)
In-Reply-To: <6599ad830802230709m5f0cbf8aia2710bd832408ba7@mail.gmail.com>

Paul M wrote:
> I'm don't think that either of these would be enough to justify big
> changes to cpusets or cgroups, although eliminating bloat is always a
> good thing.

My "tiny cpuset" idea doesn't so much eliminate bloat, as provide a
thin alternative, along side of the existing fat alternative.  So
far as kernel source goes, it would get bigger, not smaller, with now
two CONFIG choices for cpusets, fat or tiny.

The odds are, however, given that one of us has just promised not to
code this, and the other of us doesn't figure it's worth it, this
idea will not live long.  Someone would have to step up from the
embedded side with a coded version that saved a nice chunk of memory
(from their perspective) to get this off the ground, and no telling
whether even that would meet with a warm reception.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.940.382.4214

  reply	other threads:[~2008-02-23 15:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-23 12:09 Tiny cpusets -- cpusets for small systems? Paul Jackson
2008-02-23 15:09 ` Paul Menage
2008-02-23 15:57   ` Paul Jackson [this message]
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

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=20080223095752.25c1ba28.pj@sgi.com \
    --to=pj@sgi.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=kosaki.motohiro@jp.fujitsu.com \
    --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=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