public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: David Wysochanski <davidw@netapp.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Matt Domsch <Matt_Domsch@dell.com>,
	linux-scsi@vger.kernel.org
Subject: Re: SNIA iSCSI Management API Public Review
Date: Tue, 26 Oct 2004 21:23:11 +0100	[thread overview]
Message-ID: <20041026202311.GA17844@infradead.org> (raw)
In-Reply-To: <417EAC8F.5010109@netapp.com>

On Tue, Oct 26, 2004 at 03:59:11PM -0400, David Wysochanski wrote:
> Christoph Hellwig wrote:
> >On Tue, Oct 26, 2004 at 01:29:14PM -0500, Matt Domsch wrote:
> > > FYI.
> >
> >It has the usual SNIA spec quality - aka totally useless.
> >
> 
> What specifically is so bad to describe it as totally useless?

it throws far too much things together, own type and object system,
functions to deal with firmware.  there's ill suited abstractions like
the phba, etc..

as I said it's the usual SNIA design by commitee mess.

> (Note that this API isn't kernel related.)

actual it is - as most of the calls end up in an device driver,
or because the API is totally messed up with networking bits the
networking layer.

to take a very concrete example:

IMA_SetSubnetMask (sets the subnet mask for a specified network port)
doesn't make any sense at all in Linux with a software iscsi implementation
as IP addresses and thus netmasks aren't bound to network interfaces at all.


  reply	other threads:[~2004-10-26 20:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-26 18:29 SNIA iSCSI Management API Public Review Matt Domsch
2004-10-26 19:49 ` Christoph Hellwig
2004-10-26 19:59   ` David Wysochanski
2004-10-26 20:23     ` Christoph Hellwig [this message]
2004-10-26 21:04       ` David Wysochanski
2004-10-26 21:07         ` Christoph Hellwig

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=20041026202311.GA17844@infradead.org \
    --to=hch@infradead.org \
    --cc=Matt_Domsch@dell.com \
    --cc=davidw@netapp.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