From: Eric Dumazet <eric.dumazet@gmail.com>
To: "H.K. Jerry Chu" <hkchu@google.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH] Break up the single NBD lock into one per NBD device
Date: Thu, 06 Oct 2011 21:53:43 +0200 [thread overview]
Message-ID: <1317930823.3457.24.camel@edumazet-laptop> (raw)
In-Reply-To: <1317080052-6052-1-git-send-email-hkchu@google.com>
Le lundi 26 septembre 2011 à 16:34 -0700, H.K. Jerry Chu a écrit :
> From: Jerry Chu <hkchu@google.com>
>
> This patch breaks up the single NBD lock into one per
> disk. The single NBD lock has become a serious performance
> bottleneck when multiple NBD disks are being used.
>
> The original comment on why a single lock may be ok no
> longer holds for today's much faster NICs.
>
> Signed-off-by: H.K. Jerry Chu <hkchu@google.com>
> ---
> drivers/block/nbd.c | 22 +++++++++-------------
> 1 files changed, 9 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c
> index f533f33..355e15c 100644
> --- a/drivers/block/nbd.c
> +++ b/drivers/block/nbd.c
> @@ -58,20 +58,9 @@ static unsigned int debugflags;
>
> static unsigned int nbds_max = 16;
> static struct nbd_device *nbd_dev;
> +static spinlock_t *nbd_locks;
static spinlock_t *nbd_locks __read_mostly;
> static int max_part;
>
> -/*
> - * Use just one lock (or at most 1 per NIC). Two arguments for this:
> - * 1. Each NIC is essentially a synchronization point for all servers
> - * accessed through that NIC so there's no need to have more locks
> - * than NICs anyway.
> - * 2. More locks lead to more "Dirty cache line bouncing" which will slow
> - * down each lock to the point where they're actually slower than just
> - * a single lock.
> - * Thanks go to Jens Axboe and Al Viro for their LKML emails explaining this!
> - */
> -static DEFINE_SPINLOCK(nbd_lock);
> -
> #ifndef NDEBUG
> static const char *ioctl_cmd_to_ascii(int cmd)
> {
> @@ -753,6 +742,12 @@ static int __init nbd_init(void)
> if (!nbd_dev)
> return -ENOMEM;
>
> + nbd_locks = kcalloc(nbds_max, sizeof(*nbd_locks), GFP_KERNEL);
> + if (!nbd_locks) {
> + kfree(nbd_dev);
> + return -ENOMEM;
> + }
> +
Please add loop to init spinlocks to help LOCKDEP...
for (i = 0; i < nbds_max; i++)
spin_lock_init(&nbd_locks[i]);
> part_shift = 0;
> if (max_part > 0) {
> part_shift = fls(max_part);
> @@ -784,7 +779,7 @@ static int __init nbd_init(void)
> * every gendisk to have its very own request_queue struct.
> * These structs are big so we dynamically allocate them.
> */
> - disk->queue = blk_init_queue(do_nbd_request, &nbd_lock);
> + disk->queue = blk_init_queue(do_nbd_request, &nbd_locks[i]);
> if (!disk->queue) {
> put_disk(disk);
> goto out;
> @@ -832,6 +827,7 @@ out:
> put_disk(nbd_dev[i].disk);
> }
> kfree(nbd_dev);
> + kfree(nbd_locks);
> return err;
> }
>
next prev parent reply other threads:[~2011-10-06 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 23:34 [PATCH] Break up the single NBD lock into one per NBD device H.K. Jerry Chu
2011-10-06 19:37 ` David Miller
2011-10-06 19:53 ` Eric Dumazet [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-04 15:55 Nicholas Thomas
2013-02-05 14:51 ` Jerry Chu
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=1317930823.3457.24.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=hkchu@google.com \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox