From: NeilBrown <neilb@suse.de>
To: Chao Yu <chao2.yu@samsung.com>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] md: avoid potential long delay under pers_lock
Date: Fri, 26 Sep 2014 10:36:20 +1000 [thread overview]
Message-ID: <20140926103620.7c397832@notabene.brown> (raw)
In-Reply-To: <002801cfd892$696e39d0$3c4aad70$@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]
On Thu, 25 Sep 2014 15:28:34 +0800 Chao Yu <chao2.yu@samsung.com> wrote:
> printk may cause long time lapse if value of printk_delay in sysctl is
> configured large by user. If register_md_personality takes long time to print in
> spinlock pers_lock, we may encounter high CPU usage rate when there are other
> pers_lock competitors who may be blocked to spin.
> We can avoid this condition by moving printk out of coverage of pers_lock
> spinlock.
>
> Signed-off-by: Chao Yu <chao2.yu@samsung.com>
> ---
> drivers/md/md.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/md/md.c b/drivers/md/md.c
> index e02de05..5fcf215 100644
> --- a/drivers/md/md.c
> +++ b/drivers/md/md.c
> @@ -7200,9 +7200,10 @@ static const struct file_operations md_seq_fops = {
>
> int register_md_personality(struct md_personality *p)
> {
> + printk(KERN_INFO "md: %s personality registered for level %d\n",
> + p->name, p->level);
> spin_lock(&pers_lock);
> list_add_tail(&p->list, &pers_list);
> - printk(KERN_INFO "md: %s personality registered for level %d\n", p->name, p->level);
> spin_unlock(&pers_lock);
> return 0;
> }
I'm not sure I see the pressing need for this - have you noticed actual
problems?
However it seems to make sense so I've applied it.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-09-26 0:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 7:28 [PATCH] md: avoid potential long delay under pers_lock Chao Yu
2014-09-25 16:51 ` Henrique de Moraes Holschuh
2014-09-26 8:56 ` Chao Yu
2014-09-26 0:36 ` NeilBrown [this message]
2014-09-26 8:59 ` Chao Yu
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=20140926103620.7c397832@notabene.brown \
--to=neilb@suse.de \
--cc=chao2.yu@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
/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.