From: Boaz Harrosh <bharrosh@panasas.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
open-osd <osd-dev@open-osd.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Al Viro <viro@ZenIV.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
"Welch, Brent" <welch@panasas.com>,
"Bhamare, Sachin" <sbhamare@panasas.com>,
Stable Tree <stable@vger.kernel.org>
Subject: Re: [PATCH 1/1] osd_uld: Bump MAX_OSD_DEVICES from 64 to 1,048,576
Date: Wed, 1 Feb 2012 17:50:30 +0200 [thread overview]
Message-ID: <4F295F46.2010106@panasas.com> (raw)
In-Reply-To: <4F205B42.9020200@panasas.com>
On 01/25/2012 09:42 PM, Boaz Harrosh wrote:
>
> It used to be that minors where 8 bit. But now they
> are actually 20 bit. So the fix is simplicity itself.
>
> I've tested with 300 devices and all user-mode utils
> work just fine. I have also mechanically added 10,000
> to the ida (so devices are /dev/osd10000, /dev/osd10001 ...)
> and was able to mkfs an exofs filesystem and access osds
> from user-mode.
>
> All the open-osd user-mode code uses the same library
> to access devices through their symbolic names in
> /dev/osdX so I'd say it's pretty safe. (Well tested)
>
> This patch is very important because some of the systems
> that will be deploying the 3.2 pnfs-objects code are larger
> than 64 OSDs and will stop to work properly when reaching
> that number.
>
> CC: Stable <stable@vger.kernel.org>
> Signed-off-by: Boaz Harrosh <bharrosh@panasas.com>
James Hi
You never came back to me on this patch. It is very important for the
setups all this osd stuff is intended for. It is a simple bug right in the
middle of the system, which makes it useless. (I'm so embarrassed I made it
in the first place)
I have put it in today's linux-next, so it can collect dust there.
Please tell me if you want to carry this for this rc-fixes or I should
push it through the osd tree.
Thanks
Boaz
> ---
> drivers/scsi/osd/osd_uld.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/scsi/osd/osd_uld.c b/drivers/scsi/osd/osd_uld.c
> index b31a8e3..d4ed9eb 100644
> --- a/drivers/scsi/osd/osd_uld.c
> +++ b/drivers/scsi/osd/osd_uld.c
> @@ -69,10 +69,10 @@
> #ifndef SCSI_OSD_MAJOR
> # define SCSI_OSD_MAJOR 260
> #endif
> -#define SCSI_OSD_MAX_MINOR 64
> +#define SCSI_OSD_MAX_MINOR MINORMASK
>
> static const char osd_name[] = "osd";
> -static const char *osd_version_string = "open-osd 0.2.0";
> +static const char *osd_version_string = "open-osd 0.2.1";
>
> MODULE_AUTHOR("Boaz Harrosh <bharrosh@panasas.com>");
> MODULE_DESCRIPTION("open-osd Upper-Layer-Driver osd.ko");
prev parent reply other threads:[~2012-02-01 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 19:40 [PATCHSET 0/1] osd_uld: Important fix also for 3.2 Stable Boaz Harrosh
2012-01-25 19:42 ` [PATCH 1/1] osd_uld: Bump MAX_OSD_DEVICES from 64 to 1,048,576 Boaz Harrosh
2012-02-01 15:50 ` Boaz Harrosh [this message]
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=4F295F46.2010106@panasas.com \
--to=bharrosh@panasas.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=osd-dev@open-osd.org \
--cc=sbhamare@panasas.com \
--cc=stable@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
--cc=welch@panasas.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.