public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Wilck <martin.wilck@fujitsu-siemens.com>
To: "Moore, Eric" <Eric.Moore@lsil.com>
Cc: linux-scsi@vger.kernel.org,
	mpt_linux_developer <mpt_linux_developer@lsil.com>
Subject: Re: [PATCH] scsi/mptsas: add RAID devices in ascending ID order
Date: Mon, 25 Sep 2006 11:59:29 +0200	[thread overview]
Message-ID: <4517A881.3000903@fujitsu-siemens.com> (raw)
In-Reply-To: <664A4EBB07F29743873A87CF62C26D7032D5CF@NAMAIL4.ad.lsil.com>

Hi Eric,

thanks for your response.

>>    The patch makes sure that arrays are added in ascending
>>    VolumeID order.
> 
> Rejected.  
> 
> Ascending ID ordering does not address all cases. 
> There is no guarantee which target ids are 
> assigned by firmware to volumes when
> volumes are created.  

That's what my patch was supposed to handle: No matter what the ordering 
of IDs by firmware is, the devices are registered in ascending ID order.

> I've made similar 
> ordering proposals before to this mailing list. 
> All been rejected.

Do you have a thread reference for me? I'd like to understand the 
arguments better. I find this strange because scanning in ascending 
order has always been the common case in drivers as well as in the mid 
layer, AFAIK.

> I suggest that you not map your devices
> to /dev/sda, but instead use persistent
> device labels or names.  Most distro's
> now days ship with Logical Volume Manager
> that does this for you.

I know it. The problem is that there are important distros out there 
that do support persistent device names and LVM, but don't enable them 
by  default. My patch was intended to implement the "principle of least 
surprise" for users of such distributions with little experience.
More so because mptspi and mptsas behave differently; the problem
I was talking about is currently only encountered with mptsas.

Regards,
Martin

-- 
Martin Wilck                Phone: +49 5251 8 15113
Fujitsu Siemens Computers   Fax:   +49 5251 8 20409
Heinz-Nixdorf-Ring 1        mailto:Martin.Wilck@Fujitsu-Siemens.com
D-33106 Paderborn           http://www.fujitsu-siemens.com/primergy

  reply	other threads:[~2006-09-25  9:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-22 18:17 [PATCH] scsi/mptsas: add RAID devices in ascending ID order Moore, Eric
2006-09-25  9:59 ` Martin Wilck [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-26 18:33 Moore, Eric
2006-09-25 16:14 Moore, Eric
2006-09-26 12:12 ` Martin Wilck
2006-09-22 14:57 martin.wilck

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=4517A881.3000903@fujitsu-siemens.com \
    --to=martin.wilck@fujitsu-siemens.com \
    --cc=Eric.Moore@lsil.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mpt_linux_developer@lsil.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