linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Andries.Brouwer@cwi.nl
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	pbadari@us.ibm.com
Subject: Re: [patch for playing] Patch to support 4000 disks and maintain backward compatibility
Date: 11 Apr 2003 14:12:18 -0500	[thread overview]
Message-ID: <1050088340.1750.205.camel@mulgrave> (raw)
In-Reply-To: <UTC200304111807.h3BI7Or07403.aeb@smtp.cwi.nl>

On Fri, 2003-04-11 at 13:07, Andries.Brouwer@cwi.nl wrote:
> It is just that Badari and I were talking about the numbering scheme
> index = next_index++ and he pointed out that the current system
> has a certain weak number preservation guarantee that this
> index = next_index++ does not have. True.

Yes. I was just pointing out this was a byproduct of our compaction
requirement in 8:8, not necessarily a guarantee I think needs
preserving.

> It is me who wants compatibility as far as 8+8 device numbers are
> concerned, while I can see lots of ways to use new number space.

This, I'm not too sure about.  I see the value to kernel developers who
boot between different versions of the kernel, but I think when 2.6 goes
live and ships to end users, it's better not to have such numeric
equivalency crufting up the SCSI interfaces.

James



  reply	other threads:[~2003-04-11 19:00 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-11 18:07 [patch for playing] Patch to support 4000 disks and maintain backward compatibility Andries.Brouwer
2003-04-11 19:12 ` James Bottomley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-13 13:59 Paul McKenney
2003-04-12  1:13 Paul McKenney
2003-04-12 14:14 ` James Bottomley
2003-04-11 21:13 Andries.Brouwer
2003-04-11 19:45 Andries.Brouwer
2003-04-11 20:14 ` James Bottomley
2003-04-11 23:21   ` Joel Becker
2003-04-11 11:42 Andries.Brouwer
2003-04-11 14:33 ` James Bottomley
2003-04-11 16:21   ` Badari Pulavarty
2003-04-11  0:13 Andries.Brouwer
2003-04-10 23:53 Andries.Brouwer
2003-04-11  1:09 ` Badari Pulavarty
2003-04-11 10:09   ` Douglas Gilbert
2003-04-11 16:12     ` Badari Pulavarty
2003-04-10 23:33 Andries.Brouwer
2003-04-10 23:37 ` Badari Pulavarty
2003-04-10 23:09 Andries.Brouwer
2003-04-10 23:16 ` Badari Pulavarty
2003-04-10 22:09 Andries.Brouwer
2003-04-10 22:22 ` Badari Pulavarty
2003-04-10 23:57 ` Roman Zippel
2003-04-10 20:39 Badari Pulavarty
2003-04-10 20:54 ` Randy.Dunlap
2003-04-11  0:08 ` Roman Zippel
2003-04-11  1:25   ` Badari Pulavarty
2003-04-11 15:43     ` Joel Becker

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=1050088340.1750.205.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=pbadari@us.ibm.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;
as well as URLs for NNTP newsgroup(s).