From: Badari Pulavarty <pbadari@us.ibm.com>
To: Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [patch for playing] Patch to support 4000 disks and maintain backward compatibility
Date: Thu, 10 Apr 2003 18:09:55 -0700 [thread overview]
Message-ID: <200304101809.55311.pbadari@us.ibm.com> (raw)
In-Reply-To: <UTC200304102353.h3ANrXv10792.aeb@smtp.cwi.nl>
On Thursday 10 April 2003 04:53 pm, Andries.Brouwer@cwi.nl wrote:
> From: Badari Pulavarty <pbadari@us.ibm.com>
>
> > I am more worried about names slipping. I atleast hope
> > to see device names not changing by just doing
> > rmmod/insmod.
> >
> > But you see, the present sd_index_bits[] gives no such
> > guarantee. In sd_detach a bit is cleared, in sd_attach
> > the first free bit is given out. There is no memory.
>
> But the disks are probed in the same manner as last time
> (if the disks/controllers are not moved, crashed etc..).
> So we will end up getting same names.
>
> Oh, but if next_index is 0 in the module (or reset by the
> init_module code), then also with index = next_index++
> things will be the same after rmmod/insmod.
Here is my problem..
#insmod ips.o
< found 10 disks>
#insmod qla2300.o
< found 10 disks>
#rmmod ips.o
<removed 10 disks>
#insmod ips.o
<found 10 disks - but new names>
- Badari
next prev parent reply other threads:[~2003-04-11 1:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 23:53 [patch for playing] Patch to support 4000 disks and maintain backward compatibility Andries.Brouwer
2003-04-11 1:09 ` Badari Pulavarty [this message]
2003-04-11 10:09 ` Douglas Gilbert
2003-04-11 16:12 ` Badari Pulavarty
-- 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 18:07 Andries.Brouwer
2003-04-11 19:12 ` James Bottomley
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: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=200304101809.55311.pbadari@us.ibm.com \
--to=pbadari@us.ibm.com \
--cc=Andries.Brouwer@cwi.nl \
--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).