public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: "Smart, James" <James.Smart@Emulex.com>
Cc: Linux SCSI Reflector <linux-scsi@vger.kernel.org>
Subject: Re: HBAAPI
Date: Thu, 8 Apr 2004 15:25:51 +0100	[thread overview]
Message-ID: <20040408142551.GA18329@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <3356669BBE90C448AD4645C843E2BF2802C01631@xbl.ma.emulex.com>

On Thu, Apr 08, 2004 at 09:12:13AM -0400, Smart, James wrote:
> We have a fair number of ioctls which provide the functionality of HBAAPI.
> HBAAPI is a user-level API for interacting with/configuring FC HBAs. There
> are similar efforts occuring for iSCSI, etc.
> 
> The jist of HBAAPI is that each vendor supplies a "provider" module that
> implements the API for the specific hardware. Ours converts into a lot of
> ioctls. We see this as a great opportunity to remove the need for a
> vendor-specific provider module, and simply have a standard API, supported
> by linux FC drivers. There is already a sample application and template
> provider over on SourceForge that can be leveraged. We are offering to ante
> up a proposal for this API. 
> 
> Has there been any thoughts/efforts in doing this in the past ? Any
> recommendations for how this should be implemented ?  Any general thoughts?

I know this is going to sound a little weird, but take a look at
ethtool_ops (net/core/ethtool.c).  There's a certain amount of cruft
because it was done badly initially and drivers needed to be converted
gradually, but that shouldn't be necessary for a new API.

If all FC/iSCSI drivers have a scsihba_ops API, then at least we
can have typesafe APIs within the kernel for configuring this stuff.
All the parsing gets handled in one place.  It makes the discussion
about how/what/why to expose to userland a different issue ...

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain

  parent reply	other threads:[~2004-04-08 14:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08 13:12 HBAAPI Smart, James
2004-04-08 13:56 ` HBAAPI James Bottomley
2004-04-08 14:25 ` Matthew Wilcox [this message]
2004-04-16 12:10 ` HBAAPI Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2004-04-08 15:57 HBAAPI Andreas Herrmann

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=20040408142551.GA18329@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=James.Smart@Emulex.com \
    --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