From: mikem <mikem@beardog.cca.cpqcorp.net>
To: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: CSMI questions
Date: Tue, 22 Feb 2005 11:16:56 -0600 [thread overview]
Message-ID: <20050222171656.GA5953@beardog.cca.cpqcorp.net> (raw)
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.
We've also been looking at how to use sysfs rather than ioctls.
Some look reasonable, others seem to be restricted by sysfs itself.
1. only ASCII files are allowed
2. if multiple attributes are contained in one file, who parses out the data?
3. one buffer of size (PAGE_SIZE) may not hold all of the data required
Maybe I'm missing something. If any sysfs experts would like to help me
understand, I'm all ears.
The spec is available at: http://www.t10.org/ftp/t10/document.04/04-345r1.pdf
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.
next reply other threads:[~2005-02-22 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 17:16 mikem [this message]
2005-02-22 23:14 ` Greg KH
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=20050222171656.GA5953@beardog.cca.cpqcorp.net \
--to=mikem@beardog.cca.cpqcorp.net \
--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
all inboxes | Powered by JetHome®