LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Paul Clements <paul.clements@steeleye.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] NBD: raise max number of nbd devices to 1024
Date: Tue, 29 Jan 2008 13:54:17 -0800	[thread overview]
Message-ID: <20080129135417.e20b8107.akpm@linux-foundation.org> (raw)
In-Reply-To: <479F9B12.8010207@steeleye.com>

On Tue, 29 Jan 2008 16:30:58 -0500
Paul Clements <paul.clements@steeleye.com> wrote:

> The limit was 128. This changes it to 1024.
> 

Please include the "why" in changelogs as well as the "what".  It's fairly
easy to guess why this needs to be increased, but it would be useful and
interesting to hear about the operational scenarios in which 128 was
insufficient.

> 
> --- ./include/linux/nbd.h.TIMEOUT	2007-08-22 13:18:12.000000000 -0400
> +++ ./include/linux/nbd.h	2008-01-29 14:35:17.000000000 -0500
> @@ -35,7 +35,7 @@ enum {
>  };
>  
>  #define nbd_cmd(req) ((req)->cmd[0])
> -#define MAX_NBD 128
> +#define MAX_NBD 1024
>  
>  /* userspace doesn't need the nbd_device structure */
>  #ifdef __KERNEL__
> 

But one still needs to specify the nbds_max module parameter.

Can't we just nuke MAX_NBD altogether?


--- a/drivers/block/nbd.c~a
+++ a/drivers/block/nbd.c
@@ -54,7 +54,7 @@ static unsigned int debugflags;
 #endif /* NDEBUG */
 
 static unsigned int nbds_max = 16;
-static struct nbd_device nbd_dev[MAX_NBD];
+static struct nbd_device *nbd_dev;
 
 /*
  * Use just one lock (or at most 1 per NIC). Two arguments for this:
@@ -651,12 +651,6 @@ static int __init nbd_init(void)
 
 	BUILD_BUG_ON(sizeof(struct nbd_request) != 28);
 
-	if (nbds_max > MAX_NBD) {
-		printk(KERN_CRIT "nbd: cannot allocate more than %u nbds; %u requested.\n", MAX_NBD,
-				nbds_max);
-		return -EINVAL;
-	}
-
 	for (i = 0; i < nbds_max; i++) {
 		struct gendisk *disk = alloc_disk(1);
 		if (!disk)
@@ -715,6 +709,10 @@ out:
 static void __exit nbd_cleanup(void)
 {
 	int i;
+
+	nbd_dev = kcalloc(nbds_max, sizeof(*nbd_dev), GFP_KERNEL);
+	if (!nbd_dev)
+		return -ENOMEM;
 	for (i = 0; i < nbds_max; i++) {
 		struct gendisk *disk = nbd_dev[i].disk;
 		nbd_dev[i].magic = 0;
diff -puN include/linux/nbd.h~a include/linux/nbd.h
--- a/include/linux/nbd.h~a
+++ a/include/linux/nbd.h
@@ -35,7 +35,6 @@ enum {
 };
 
 #define nbd_cmd(req) ((req)->cmd[0])
-#define MAX_NBD 128
 
 /* userspace doesn't need the nbd_device structure */
 #ifdef __KERNEL__
_


much nicer?


  reply	other threads:[~2008-01-29 21:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-29 21:30 Paul Clements
2008-01-29 21:54 ` Andrew Morton [this message]
2008-01-30  2:04   ` Paul Clements
2008-01-30  2:08     ` Andrew Morton
2008-01-30 13:14       ` Paul Clements

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=20080129135417.e20b8107.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.clements@steeleye.com \
    --subject='Re: [PATCH 1/1] NBD: raise max number of nbd devices to 1024' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).