mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kurt Garloff <garloff@suse.de>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: 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 23:11:10 +0200	[thread overview]
Message-ID: <20020722211110.GL19587@nbkurt.etpnet.phys.tue.nl> (raw)
In-Reply-To: <20020722164856.D19904@devserv.devel.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2687 bytes --]

Hi Pete,

On Mon, Jul 22, 2002 at 04:48:56PM -0400, Pete Zaitcev wrote:
> > From: Kurt Garloff <garloff@suse.de>
> 
> > > For those who do not follow, John Cagle allocated 8 more SCSI
> > > disk majors.
> > 
> > Have those officially been assigned to SCSI disks?
> > So disks 128 -- 255 have majors 128 thr. 135?
> 
> I do not understand what your problem is. Do you refuse to recognise
> John as the LANANA chair or something?

Strange. I was just asking. Why would you think I would be silly and
refuse to recognize somebody?

> My patch is done in accordance with this:
> http://www.lanana.org/docs/device-list/devices.txt

OK, I should have checked there before asking here, probably.

> > 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.

There will be.

> This is why Arjan filed for and received
> additional majors. Dynamic solutions need some time to float about
> the community, I think.

I don't object to having some more static ones. Fewer users will need
userspace tools for handling the dev nodes then ;-)
And of course, I'll adapt my patch to grab the assigned ones before
the unknown ones ...

> BTW, DASD does the same thing already. I never saw any memo or document
> explaining how to use this capability properly. Perhaps SuSE people
> support it. Kurt, can you tell anything about it?

I don't know much about DASD. They allocate block majors dynamically
starting from 255 backwards as far as I know. So, dev nodes need to
be created dynamically, I guess.

> > Do you have any idea why we can't just sync all mounted filesystems
> > in do_emergency_sync()?
> >  DASD? LVM? EVMS? MD? Loop? NBD? DRBD? What's the rationale 
> > of restricting the sync to only IDE and SCSI? Deadlock avoidance?
> 
> I suspect it is a deadlock prevention thing, too. I cannot say if
> it ever worked satisfactory... :)

Well, Alt-SysRq-S does work; but it obviously misses to sync a number
of filesystems.

> > I'm gonna post my patches tomorrow ...
> 
> Thanks, that's interesting. Like I said, they are not likely to
> get to the distro soon, but I'd love to look at them.

Well, I would be astonished if you adopted before we do ;-)

Regards,
-- 
Kurt Garloff  <garloff@suse.de>                          Eindhoven, NL
GPG key: See mail header, key servers         Linux kernel development
SuSE Linux AG, Nuernberg, DE                            SCSI, Security

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2002-07-22 21:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020720195729.C20953@devserv.devel.redhat.com>
2002-07-22 17:08 ` Kurt Garloff
2002-07-22 20:48   ` Pete Zaitcev
2002-07-22 20:57     ` Christoph Hellwig
2002-07-22 21:12       ` Kurt Garloff
2002-07-22 21:11     ` Kurt Garloff [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=20020722211110.GL19587@nbkurt.etpnet.phys.tue.nl \
    --to=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

all inboxes | Powered by JetHome®