public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Kurt Garloff <garloff@suse.de>,
	Linux SCSI list <linux-scsi@vger.kernel.org>,
	Linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Patch for 256 disks in 2.4
Date: Mon, 22 Jul 2002 21:57:00 +0100	[thread overview]
Message-ID: <3566.42994233898$1027371630@news.gmane.org> (raw)
In-Reply-To: <20020722164856.D19904@devserv.devel.redhat.com>; from zaitcev@redhat.com on Mon, Jul 22, 2002 at 04:48:56PM -0400

On Mon, Jul 22, 2002 at 04:48:56PM -0400, Pete Zaitcev wrote:
> > I've written a patch for sd that makes the allocation of majors
> > dynamic. The driver just takes 8 at sd_init and further majors are 
> > allocated when disks are attached. Which saves a lot of memory for
> > all the gendisk and hd_struct stuff in case you do not have a lot of 
> > SCSI disks connected. The patch does support up to 160 SD majors, 
> > though currently, it won't succeed getting more than 132 majors.
> 
> That's wonderful, but we cannot ship that. There is no userland
> support to create device nodes in dynamic fashion and to ensure
> that they do not conflict. This is why Arjan filed for and received
> additional majors. Dynamic solutions need some time to float about
> the community, I think.

I might be stupid, but it looks to me like we want both the new majors
and the kernel structs dynamically allocated when they get actually used..


  reply	other threads:[~2002-07-22 20:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-20 23:57 Patch for 256 disks in 2.4 Pete Zaitcev
2002-07-22 17:08 ` Kurt Garloff
2002-07-22 20:48   ` Pete Zaitcev
2002-07-22 20:57     ` Christoph Hellwig [this message]
2002-07-22 21:11     ` Kurt Garloff
     [not found]     ` <20020722215700.A12813@infradead.org>
2002-07-22 21:12       ` 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='3566.42994233898$1027371630@news.gmane.org' \
    --to=hch@infradead.org \
    --cc=garloff@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=zaitcev@redhat.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