From: Patrick Mansfield <patmans@us.ibm.com>
To: Douglas Gilbert <dougg@torque.net>
Cc: linux-scsi@vger.kernel.org, sdake@mvista.com, Joel.Becker@oracle.com
Subject: Re: Fwd: 32bit dev_t
Date: Wed, 22 Jan 2003 09:18:15 -0800 [thread overview]
Message-ID: <20030122091815.A32098@beaverton.ibm.com> (raw)
In-Reply-To: <3E2DC21D.9010204@torque.net>; from dougg@torque.net on Wed, Jan 22, 2003 at 08:56:45AM +1100
On Wed, Jan 22, 2003 at 08:56:45AM +1100, Douglas Gilbert wrote:
> This post appeared recently on the linux kernel list.
> What is the maximum number of disks that can be attached
> in lk 2.5? Is it 256 (double the number of SCSI disk majors)
> or larger. I remember Richard Gooch's "sd-many" patch
> was rejected for 2.5 because it was said there was a
> better mechanism around the corner.
>
> BTW when I tested 129 (1 real + 128 dummies) disks with
> scsi_debug there was a problem the last one. Has anyone
> tested > 128 disks in lk 2.5?
>
> Doug Gilbert
It should be 16 sd majors * 16 disks per major = 256.
What was the problem with scsi_debug? I thought you got it past 128 LUNs
at some point. There are no longer kmalloc (or vmalloc) issues with sd.c.
-- Patrick Mansfield
next prev parent reply other threads:[~2003-01-22 17:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 21:56 Fwd: 32bit dev_t Douglas Gilbert
2003-01-22 17:18 ` Patrick Mansfield [this message]
2003-01-22 23:55 ` Tim Pepper
2003-01-23 0:51 ` Joel Becker
2003-01-23 18:31 ` Kurt Garloff
2003-01-23 22:18 ` Christoph Hellwig
2003-01-24 8:20 ` Kurt Garloff
2003-01-24 18:29 ` Joel Becker
2003-01-27 22:51 ` Christoph Hellwig
2003-01-28 11:21 ` Alan Cox
2003-01-28 11:28 ` Christoph Hellwig
2003-01-28 15:19 ` Kurt Garloff
2003-01-28 16:33 ` Bryan Henderson
2003-01-28 18:22 ` Alan Cox
2003-01-28 17:09 ` New model for managing dev_t's for partitionable block devices Steven Dake
2003-01-29 1:41 ` Bryan Henderson
2003-01-29 16:45 ` Steven Dake
2003-01-29 17:38 ` Andries Brouwer
2003-01-29 18:00 ` Kurt Garloff
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=20030122091815.A32098@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=Joel.Becker@oracle.com \
--cc=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=sdake@mvista.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