public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian King <brking@linux.vnet.ibm.com>
To: "Mukker, Atul" <Atul.Mukker@lsi.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: Recommended HBA management interfaces
Date: Fri, 17 Jul 2009 10:35:49 -0500	[thread overview]
Message-ID: <4A609A55.9040404@linux.vnet.ibm.com> (raw)
In-Reply-To: <6C678488C5CEE74F813A4D1948FD2DC7A998698F@cosmail02.lsi.com>

Mukker, Atul wrote:
> Hi All,
> 
> We would like expert comments on the following questions regarding
> management of HBA from applications.
> 
> Traditionally, our drivers create a character device node, whose
> file_operations are then used by the management applications to
> transfer HBA specific commands. In addition to being quirky, this
> interface has a few limitations which we would like to remove, most
> important being able to seamlessly handle asynchronous events with
> data transfer.
> 
> 1. What is (are) the other standard/recommended interfaces which
> applications can use to transfer HBA specific commands and data.

Depends on what the commands look like. With ipr, the commands that
the management application need to send to the HBA look sufficiently
like SCSI that I was able to report an sg device node for the adapter
and use SG_IO to send these commands.

sysfs, debugfs, and configfs are options as well.


> 2. How should an LLD implement interfaces to transmit asynchronous
> information to the management applications? The requirement is to be
> able to transmit data buffer as well as notifications for events.

I've had good success with netlink. In my use I only send a notification
to userspace and let the application send some commands to figure out
what happened, but netlink does allow to send data as well. It makes it very
easy to have multiple concurrent readers of the data, which I've found very
useful.

> 3. The interface should be able to work even if no SCSI devices are
> exported to the kernel.

netlink allows this.

> 4. Should work seamlessly across vmware and xen kernels.

netlink should work here too.

-Brian

-- 
Brian King
Linux on Power Virtualization
IBM Linux Technology Center



  reply	other threads:[~2009-07-17 15:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-17 13:16 Recommended HBA management interfaces Mukker, Atul
2009-07-17 15:35 ` Brian King [this message]
2009-07-20 16:28   ` Mukker, Atul
2009-07-20 16:57     ` James Smart
2009-07-20 18:03       ` Mukker, Atul
2009-07-20 19:08         ` James Smart
2009-07-20 20:33           ` Mukker, Atul
2009-07-21 12:29             ` James Smart
2009-07-21 13:38               ` Mukker, Atul
2009-07-21 13:48               ` Drew
2009-07-21 13:58                 ` Mukker, Atul
2009-07-21 14:59                   ` James Smart
2009-07-21 16:27                     ` Drew

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=4A609A55.9040404@linux.vnet.ibm.com \
    --to=brking@linux.vnet.ibm.com \
    --cc=Atul.Mukker@lsi.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