All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: hawkes@sgi.com
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
	Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>,
	Jack Steiner <steiner@sgi.com>,
	linux-kernel@vger.kernel.org,
	Christoph Lameter <clameter@sgi.com>, Paul Jackson <pj@sgi.com>,
	John Hawkes <jrhawkes@yahoo.com>
Subject: Re: [PATCH] build sched domains tracking cpusets
Date: Mon, 10 Jul 2006 14:41:09 -0700	[thread overview]
Message-ID: <20060710144109.A20509@unix-os.sc.intel.com> (raw)
In-Reply-To: <20060707193107.2870.60825.sendpatchset@tomahawk.engr.sgi.com>; from hawkes@sgi.com on Fri, Jul 07, 2006 at 12:31:07PM -0700

On Fri, Jul 07, 2006 at 12:31:07PM -0700, hawkes@sgi.com wrote:
>From: "Nick Piggin" <nickpiggin@yahoo.com.au>
>>
>> Can you get away without using the bundle? Or does it make things easier?
>> You could add a new use_count to struct sched_domain if you'd like.... 
>> does it make the setup/teardown too difficult?
>
>The use_count is a ploy to reduce the demand for 
>SCHED_DOMAIN_CPUSET_MAX 
>slots.  I have been told that one popular job manager will create some 
>duplicate cpusets.
>
>The bundle is really there to simplify discovering the sched 
>group lists.

I think we can do away with the bundle. sd has a pointer to the sched_group
and the first cpu in sd->span can free the groups list allocation.

thanks,
suresh

  reply	other threads:[~2006-07-10 21:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-07 19:31 [PATCH] build sched domains tracking cpusets hawkes
2006-07-10 21:41 ` Siddha, Suresh B [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-06 23:43 hawkes
2006-07-07  8:38 ` Nick Piggin
2006-07-07 19:05   ` John Hawkes

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=20060710144109.A20509@unix-os.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=hawkes@sgi.com \
    --cc=jrhawkes@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nickpiggin@yahoo.com.au \
    --cc=pj@sgi.com \
    --cc=steiner@sgi.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.