From: Douglas Gilbert <dougg@torque.net>
To: Lee Xing <lxing@Crossroads.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: A question on Linux SCSI low-level driver
Date: Sun, 09 May 2004 12:10:47 +1000 [thread overview]
Message-ID: <409D9327.9010000@torque.net> (raw)
In-Reply-To: <519672568F040C41B6FAC21ADF51B18FEFE3@mailnode1.commstor.crossroads.com>
Lee Xing wrote:
> Hi,
>
> We are trying to write a low-level driver (no need for a perfect one at this time, just need to register the disks and do some simple I/Os). I would sincerely appreciate it if some one could give me some information/suggestions/hints.
>
> This low-level driver has indirect (via other layers) information on physical disks, so it can only provide mid-level driver with bus number, target number and lun number of the disks. It will convert SCSI passthrough commands coming from the mid-level driver and send the converted command packages to the disks (again, via other layers). It also sends the responses coming from physical disks (via other layers) back to the mid-level driver. The "other layers" are SCSI-ready and can handle SCSI cmds/responses well.
>
> My questions are:
>
> - is it (i.e. registering the disks with mid-level driver and doing some
> simple I/Os) doable if this low-level driver only provides mid-level with
> bus/target/lun numbers (without any hardware-related information)?
Lee,
See the scsi_debug driver (either in the lk 2.4 or lk 2.6
series). It is a scsi subsystem LLD that is basically a
ram disk so there is no "hardware" information to exchange
with the mid level.
Doug Gilbert
> - what can be the potential problems (if nay)?
>
> Best Regards,
next prev parent reply other threads:[~2004-05-09 2:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-07 21:28 A question on Linux SCSI low-level driver Lee Xing
2004-05-09 2:10 ` Douglas Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-10 17:55 Lee Xing
2004-05-18 22:27 Lee Xing
2004-05-19 3:52 ` Douglas Gilbert
2004-05-19 16:14 Lee Xing
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=409D9327.9010000@torque.net \
--to=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=lxing@Crossroads.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