linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Andreas Dilger <adilger@turbolinux.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [RFT] #2 Support for ~2144 SCSI discs
Date: Thu, 2 Aug 2001 08:37:20 -0600	[thread overview]
Message-ID: <200108021437.f72EbKw18361@mobilix.ras.ucalgary.ca> (raw)
In-Reply-To: <200108020751.f727pnMf010874@webber.adilger.int>
In-Reply-To: <200108020642.f726g0L15715@mobilix.ras.ucalgary.ca> <200108020751.f727pnMf010874@webber.adilger.int>

Andreas Dilger writes:
> Richard writes:
> >   Hi, all. Below is my second cut of a patch that adds support for
> > large numbers of SCSI discs (approximately 2144). I'd like people to
> > try this out. I've fixed a couple of "minor" typos that happened to
> > disable sd detection. I've also tested this patch: it works fine on my
> > 3 drive system. In addition, I've switched to using vmalloc() for key
> > data structures, so the kmalloc() limitations shouldn't hit us. I've
> > added an in_interrupt() test to sd_init() just in case.
> 
> The real question is whether this code is limited to adding only SCSI
> major numbers, or if it could be used to assign major numbers to
> other subsystems (sorry I haven't looked at the code yet)?

This patch leverages some new infrastructure that I developed in a
recent devfs patch, and Linus included that in 2.4.7. The key
functions are <devfs_alloc_major> and <devfs_dealloc_major>. I wrote
these functions primarily for block drivers (although you can allocate
char majors as well, keeping in mind there are far fewer left
unassigned), which due to our aging block I/O layer require majors.

So, yes, you can already patch other subsystems to dynamically assign
major numbers in 2.4.7. I'd like to see people do that. My patch for
sd.c can also serve as a demonstration on how to use the new API.

>  From our discussion last week, it _should_ be able to assign major
> numbers to other systems like EVMS, which you would probably want to
> use on top of those 2144 SCSI disks anyways.  However, since you are
> billing this as the "2144 SCSI disk patch", I thought I would
> confirm.

This patch only touches sd.c. But everything you need for other
drivers is already in 2.4.7. Go forth and allocate!

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

  parent reply	other threads:[~2001-08-02 14:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-02  6:42 [RFT] #2 Support for ~2144 SCSI discs Richard Gooch
2001-08-02  7:51 ` Andreas Dilger
2001-08-02 14:37 ` Richard Gooch [this message]
2001-08-10  4:15 ` [RFT] #2 Support for ~2144 SCSI discs, scsi_debug Douglas Gilbert
2001-08-10  4:31 ` Richard Gooch
2001-08-10 12:56   ` Douglas Gilbert
2001-08-10 20:30   ` Richard Gooch
2001-08-12 22:06     ` Douglas Gilbert
2001-08-13 16:23   ` Richard Gooch
     [not found] <no.id>
2001-08-02 15:36 ` [RFT] #2 Support for ~2144 SCSI discs Alan Cox
2001-08-02 15:47 ` Richard Gooch
2001-08-02 16:34 ` Alan Cox
2001-08-02 17:00 ` Richard Gooch

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=200108021437.f72EbKw18361@mobilix.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=adilger@turbolinux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).