From: Greg KH <greg@kroah.com>
To: mikem <mikem@beardog.cca.cpqcorp.net>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: CSMI questions
Date: Tue, 22 Feb 2005 15:14:50 -0800 [thread overview]
Message-ID: <20050222231450.GB10067@kroah.com> (raw)
In-Reply-To: <20050222171656.GA5953@beardog.cca.cpqcorp.net>
On Tue, Feb 22, 2005 at 11:16:56AM -0600, mikem wrote:
> All,
> I hate to dredge this up again, but, when Eric Moore submitted changes for MPT
> Fusion driver containing the CSMI ioctls it was rejected. There was talk on
> the linux-scsi list about it being a horrible interface, among other things.
> There were also comments about there being a Linux only approach. Personally,
> I like that idea but it's not good from a business perspective. Especially
> because HP, Dell, and others support more than one OS. Having a unique set of
> management apps for each OS would be very cumbersome.
Honestly, the kernel developers don't care about cross-OS platform
management utilities from a business perspective. :)
> We've also been looking at how to use sysfs rather than ioctls.
Good.
> Some look reasonable, others seem to be restricted by sysfs itself.
> 1. only ASCII files are allowed
With 1 value in that file.
> 2. if multiple attributes are contained in one file, who parses out the data?
multiple attributes are not allowed to be contained in a single file.
> 3. one buffer of size (PAGE_SIZE) may not hold all of the data required
You have a _single_ attribute that is bigger than PAGE_SIZE? What is
it?
> I'd also like an (brief) explanation of why ioctls are so bad. I've seen the
> reasons of them never going away, etc. But from the beginning of time (UNIX)
> ioctls have been the preferred method of user space/kernel communication.
That's because there was no other method. See the lkml archives for why
ioctls are considered bad, I don't want to dredge it up again.
Hope this helps,
greg k-h
next prev parent reply other threads:[~2005-02-22 23:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 17:16 mikem
2005-02-22 23:14 ` Greg KH [this message]
2005-02-24 14:25 ` Erik Mouw
2005-02-22 18:15 Miller, Mike (OS Dev)
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=20050222231450.GB10067@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mikem@beardog.cca.cpqcorp.net \
/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®