linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luben Tuikov <luben_tuikov@adaptec.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Rik van Riel <riel@redhat.com>, Luben Tuikov <ltuikov@yahoo.com>,
	James Bottomley <James.Bottomley@SteelEye.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 2.6.13 14/14] sas-class: SCSI Host glue
Date: Tue, 13 Sep 2005 08:41:35 -0400	[thread overview]
Message-ID: <4326C8FF.8050400@adaptec.com> (raw)
In-Reply-To: <20050911094007.GB5429@infradead.org>

On 09/11/05 05:40, Christoph Hellwig wrote:
> 
> Yes, absolutely.  This discussion is driving far off right now, no one
> is asking Adaptec to add support for competing products here, we're just
> asking to not declare the host_template in the common code, and supporting
> limited controllers is one of the reasons.

Hi Christoph,

I cannot make something to be, something that it is not.

That is, the SAS LLDD is not a "scsi host" and it will never be,
because it is just not a "scsi host".

What it is, is an access point to the transport, this is its
sole function and existance.  E.g. it doesn't know about max_luns,
etc, which are purely SCSI Core-into-scsi_host concepts.
It does know about Execute Command SCSI RPC and TMFs.

The "scsi_host" template is a SCSI Core concept, which
mixes a software component (what it is) and a hardware component
(what you're talking about).

Now, see the layering infrastructure: SATA support:
The sas_sata_host.c file would also declare a scsi_host, where
it will define its own queuecommand(), eh_timed_out(),
eh_strategy_handler(), etc. and do the _protocol_ part,
whereby the SAS LLDD does the transport part.

	Luben






  reply	other threads:[~2005-09-13 12:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-09 19:42 [PATCH 2.6.13 14/14] sas-class: SCSI Host glue Luben Tuikov
2005-09-09 23:35 ` James Bottomley
2005-09-10  4:12   ` Luben Tuikov
2005-09-10 13:08     ` Arjan van de Ven
2005-09-12 13:55       ` Luben Tuikov
2005-09-12 14:13         ` Jörn Engel
2005-09-12 18:46           ` Luben Tuikov
2005-09-12 18:46       ` Luben Tuikov
2005-09-10 14:30     ` Rik van Riel
2005-09-10 20:20       ` Alan Cox
2005-09-11  9:40         ` Christoph Hellwig
2005-09-13 12:41           ` Luben Tuikov [this message]
2005-09-11  3:56       ` ak
2005-09-11 13:41         ` James Bottomley
2005-09-12 17:12           ` Luben Tuikov
2005-09-12 17:55             ` Alan Cox
2005-09-12 13:56       ` Luben Tuikov
2005-09-11  9:38     ` Christoph Hellwig
2005-09-12 16:08       ` Matthew Wilcox
2005-09-12 19:07         ` Luben Tuikov
2005-09-12 19:55           ` Matthew Wilcox
2005-09-12 23:51             ` Stefan Richter
2005-09-12 22:00       ` Luben Tuikov
2005-09-13 15:40         ` Matthew Wilcox
2005-09-14  5:56           ` Sergey Panov
2005-09-14 10:37             ` Christoph Hellwig
2005-09-14 10:53             ` Jeff Garzik
2005-09-14 12:59               ` Luben Tuikov

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=4326C8FF.8050400@adaptec.com \
    --to=luben_tuikov@adaptec.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=ltuikov@yahoo.com \
    --cc=riel@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).