From: Jeff Garzik <jeff@garzik.org>
To: FUJITA Tomonori <tomof@acm.org>
Cc: pw@osc.edu, bharrosh@panasas.com,
James.Bottomley@HansenPartnership.com,
fujita.tomonori@lab.ntt.co.jp, hch@infradead.org,
jens.axboe@oracle.com, linux-scsi@vger.kernel.org,
akpm@linux-foundation.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 21/24][RFC] scsi_tgt: use of sense accessors
Date: Tue, 05 Feb 2008 12:28:30 -0500 [thread overview]
Message-ID: <47A89CBE.6040301@garzik.org> (raw)
In-Reply-To: <20080206015308F.tomof@acm.org>
FUJITA Tomonori wrote:
> On Tue, 5 Feb 2008 11:21:33 -0500
> Pete Wyckoff <pw@osc.edu> wrote:
>
>> bharrosh@panasas.com wrote on Mon, 04 Feb 2008 19:53 +0200:
>>> FIXME: I need help with this driver (Pete?)
>>> I used scsi_sense() in a none const way. But since
>>> scsi_tgt is the ULD here, it can just access it's own sense
>>> buffer directly. I did not use scsi_eh_cpy_sense() because
>>> I did not want the extra copy. Pete will want to use a 260
>>> bytes buffer here.
>>>
>>> Signed-off-by: Boaz Harrosh <bharrosh@panasas.com>
>>> Need-help-from: Pete Wyckoff <pw@osc.edu>
>> FYI, I never use scsi_tgt. Only just pure userspace on the target,
>> and a dumb ethernet NIC that does not know it is speaking any form
>> of SCSI.
>
> Seems that many people misunderstand STGT iSCSI (and iSER), FCoE, and
> SRP (not implemented yet) software target drivers. They don't use the
> tgt kernel module. They just run in user space like user-space nfs
> daemon.
FWIW, some AHCI and other SATA chips implement ATA target mode. I'm
watching this SCSI work with interest, hoping that many of the concepts
(and code?) can be applied to SATA as well.
If for no other reason than I can build a cheap ATA protocol analyzer,
or bridge.
Jeff
prev parent reply other threads:[~2008-02-05 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 17:53 [PATCH 21/24][RFC] scsi_tgt: use of sense accessors Boaz Harrosh
2008-02-05 16:21 ` Pete Wyckoff
2008-02-05 16:53 ` FUJITA Tomonori
2008-02-05 17:28 ` Jeff Garzik [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=47A89CBE.6040301@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bharrosh@panasas.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hch@infradead.org \
--cc=jens.axboe@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=pw@osc.edu \
--cc=tomof@acm.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.