mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Lynch <ntl@pobox.com>
To: Shaohua Li <shaohua.li@intel.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Ashok Raj <ashok.raj@intel.com>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 10/10] cpu bulk removal interface
Date: Mon, 8 May 2006 01:31:30 -0500	[thread overview]
Message-ID: <20060508063130.GB9344@localdomain> (raw)
In-Reply-To: <1147067158.2760.90.camel@sli10-desk.sh.intel.com>

Shaohua Li wrote:
> 
> Interface for bulk cpu removal. It's /sys/devices/system/cpu/cpu_bulk_remove
> 
> Signed-off-by: Shaohua Li <shaohua.li@intel.com>
> ---
> 
>  linux-2.6.17-rc3-root/drivers/base/cpu.c  |   47 +++++++++++++++++++++++++++++-
>  linux-2.6.17-rc3-root/include/linux/cpu.h |    3 +
>  2 files changed, 49 insertions(+), 1 deletion(-)
> 
> diff -puN drivers/base/cpu.c~bulk_cpu_remove_interface drivers/base/cpu.c
> --- linux-2.6.17-rc3/drivers/base/cpu.c~bulk_cpu_remove_interface	2006-05-07 07:47:02.000000000 +0800
> +++ linux-2.6.17-rc3-root/drivers/base/cpu.c	2006-05-07 09:29:54.000000000 +0800
> @@ -76,6 +76,46 @@ static inline void register_cpu_control(
>  }
>  #endif /* CONFIG_HOTPLUG_CPU */
>  
> +#ifdef CONFIG_BULK_CPU_REMOVE
> +static ssize_t cpu_bulk_remove_show(struct sysdev_class *c, char *buf)
> +{
> +	int len;
> +
> +	len = cpulist_scnprintf(buf, PAGE_SIZE-1, cpu_online_map);
> +	len += sprintf(buf + len, "\n");
> +	return len;
> +}

This doesn't really seem meaningful.  I'd say the attribute could do
without a show method.

> +static ssize_t cpu_bulk_remove_store(struct sysdev_class *c,
> +	const char *buf, size_t count)
> +{
> +	int err;
> +	cpumask_t removed_cpus;
> +
> +	if ((err = lock_cpu_hotplug_interruptible() != 0))
> +		return err;
> +	err = cpulist_parse(buf, removed_cpus);
> +	if (err) {
> +		unlock_cpu_hotplug();
> +		return err;
> +	}
> +
> +	unlock_cpu_hotplug();
> +	cpu_down_mask(removed_cpus);
> +	return count;
> +}

Shouldn't this make sure that we don't offline all cpus?

Why are you using lock_cpu_hotplug_interruptible instead of
lock_cpu_hotplug?

Why is only the parsing of the cpumask buffer protected by the cpu
hotplug lock?  Shouldn't cpu_down_mask be called with the lock held?

Can cpu_down_mask fail, and if so, shouldn't we be reporting the
error?

  reply	other threads:[~2006-05-08  6:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-08  5:45 Shaohua Li
2006-05-08  6:31 ` Nathan Lynch [this message]
2006-05-08  7:43   ` Shaohua Li

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=20060508063130.GB9344@localdomain \
    --to=ntl@pobox.com \
    --cc=akpm@osdl.org \
    --cc=ashok.raj@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaohua.li@intel.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®