[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1202844495.3137.120.camel@localhost.localdomain>
Date: Tue, 12 Feb 2008 13:28:15 -0600
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: kristen.c.accardi@...el.com
Cc: ltuikov@...oo.com, linux-scsi <linux-scsi@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-ide <linux-ide@...r.kernel.org>, jeff@...zik.org
Subject: Re: [PATCH] enclosure: add support for enclosure services
On Tue, 2008-02-12 at 11:07 -0800, Kristen Carlson Accardi wrote:
> I understand what you are trying to do - I guess I just doubt the value
> you've added by doing this. I think that there's going to be so much
> customization that system vendors will want to add, that they are going
> to wind up adding a custom library regardless, so standardising those
> few things won't buy us anything.
It depends ... if you actually have a use for the customisations, yes.
If you just want the basics of who (what's in the enclousure), what
(activity) and where (locate) then I think it solves your problem almost
entirely.
So, entirely as a straw horse, tell me what else your enclosures provide
that I haven't listed in the four points. The SES standards too provide
a huge range of things that no-one ever seems to implement (temperature,
power, fan speeds etc).
I think the users of enclosures fall int these categories
85% just want to know where their device actually is (i.e. that sdc is
in enclosure slot 5)
50% like watching the activity lights
30% want to be able to have a visual locate function
20% want a visual failure indication (the other 80% rely on some OS
notification instead)
When you add up the overlapping needs, you get about 90% of people happy
with the basics that the enclosure services provide. Could there be
more ... sure; should there be more ... I don't think so ... that's what
value add the user libraries can provide.
James
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists