public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Hayter <steven@hayter.me.uk>
To: "Haefliger, Juerg" <Juerg.Haefliger@hp.com>
Cc: ltuikov@yahoo.com, linux-scsi@vger.kernel.org
Subject: Re: Mid-layer API?
Date: Mon, 23 Oct 2006 23:53:29 +0100	[thread overview]
Message-ID: <453D47E9.8000606@hayter.me.uk> (raw)
In-Reply-To: <861B5CF71BC70C478DFEB9EAFE98F699ACB0DD@G3W0068.americas.hpqcorp.net>

Haefliger, Juerg wrote:
 > Hi Luben,
 >
 > I did but I still don't get it :-) In fact I'm more confused now. Why
 > host_template? Isn't that function used to register an LLD with the
 > mid-layer? I'm trying to tap into the other side of the mid-layer.

On the driver side (HBA) you've got the host template, and queue_command().

On the other side (the interface used by sg/sd/st) used to live 
scsi_do_req() (gone in 2.6.18) which is now scsi_execute_async() and 
friends.

The header files/function templates should be fairly self-explanatory 
apart from the confusing use of old-style names, the 'void *buffer' is 
the scatter gather list, the 'unsigned buflen' is the total amount of 
data you want to transfer, and use_sg is the number of scatter-gather 
elements.

Hope that gives you some place to start with, if you just want to send 
SCSI commands into the kernel.

Regards,
Steve

      reply	other threads:[~2006-10-23 22:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18 19:43 Mid-layer API? Haefliger, Juerg
2006-10-18 20:08 ` Randy Dunlap
2006-10-19 18:54   ` Haefliger, Juerg
2006-10-20  8:06 ` Luben Tuikov
2006-10-20 15:32   ` Haefliger, Juerg
2006-10-20 17:25     ` Luben Tuikov
2006-10-20 18:25       ` question scsi_register verses register_blkdev Thayne Harmon
2006-10-20 21:03         ` Stefan Richter
2006-10-23 21:56       ` Mid-layer API? Haefliger, Juerg
2006-10-23 22:53         ` Steven Hayter [this message]

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=453D47E9.8000606@hayter.me.uk \
    --to=steven@hayter.me.uk \
    --cc=Juerg.Haefliger@hp.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=ltuikov@yahoo.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