All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: vatsa@in.ibm.com
Cc: Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>,
	suresh.b.siddha@intel.com, Dinakar Guniguntala <dino@in.ibm.com>,
	pj@sgi.com, hawkes@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.16-mm2 4/4] sched_domain: Allocate sched_group structures dynamically
Date: Sun, 02 Apr 2006 11:39:30 +1000	[thread overview]
Message-ID: <442F2B52.6000205@yahoo.com.au> (raw)
In-Reply-To: <20060401185644.GC25971@in.ibm.com>


Srivatsa Vaddagiri wrote:
>  /*
> @@ -6113,6 +6125,10 @@ next_sg:
>  static int build_sched_domains(const cpumask_t *cpu_map)
>  {
>  	int i;
> +	struct sched_group *sched_group_phys = NULL;
> +#ifdef CONFIG_SCHED_MC
> +	struct sched_group *sched_group_core = NULL;
> +#endif
>  #ifdef CONFIG_NUMA
>  	struct sched_group **sched_group_nodes = NULL;
>  	struct sched_group *sched_group_allnodes = NULL;
> @@ -6171,6 +6187,18 @@ static int build_sched_domains(const cpu
>  		cpus_and(sd->span, sd->span, *cpu_map);
>  #endif
>  
> +		if (!sched_group_phys) {
> +			sched_group_phys
> +				= kmalloc(sizeof(struct sched_group) * NR_CPUS,
> +					  GFP_KERNEL);
> +			if (!sched_group_phys) {
> +				printk (KERN_WARNING "Can not alloc phys sched"
> +						     "group\n");
> +				goto error;
> +			}
> +			sched_group_phys_bycpu[i] = sched_group_phys;
> +		}

Doesn't the last assignment have to be outside the if statement?

Hmm.. this design seems like the best way to go for now. Suresh?

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

  reply	other threads:[~2006-04-02  4:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-01 18:56 [PATCH 2.6.16-mm2 4/4] sched_domain: Allocate sched_group structures dynamically Srivatsa Vaddagiri
2006-04-02  1:39 ` Nick Piggin [this message]
2006-04-02  5:04   ` Srivatsa Vaddagiri
2006-04-02  5:21     ` Nick Piggin
2006-04-02  9:14       ` Srivatsa Vaddagiri
2006-04-02  7:35   ` Siddha, Suresh B
2006-04-02  9:17     ` Srivatsa Vaddagiri

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=442F2B52.6000205@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=dino@in.ibm.com \
    --cc=hawkes@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pj@sgi.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=vatsa@in.ibm.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.