From: Mike Christie <michaelc@cs.wisc.edu>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH RFC 1/3] SCSI Userspace Target: scsi-ml changes
Date: Mon, 06 Feb 2006 12:45:28 -0600 [thread overview]
Message-ID: <43E79948.2090004@cs.wisc.edu> (raw)
In-Reply-To: <1139250832.3022.26.camel@mulgrave.il.steeleye.com>
James Bottomley wrote:
> On Mon, 2006-02-06 at 12:22 -0600, Mike Christie wrote:
>
>>I understand. To make this worse, for the target code since we are
>>mapping data like SG_IO block layer code (we used their functions) we
>>need process context for the unmap. To handle this we added a work
>>struct on the scsi_cmnd and the work struct is pretty large and only
>>used for targets. We can move all the target specific to a:
>>
>>scsi_tgt_cmnd {
>> work;
>> host;
>>};
>>
>>And store out scsi_tgt_cmnd in the scsi_cmnd->host_scribble or somewhere
>>on the SCp. Is that too hacky?
>
>
> Could you take a look at the execute_in_user_context() function I'm
> hatching to add to the workqueue here:
>
> http://marc.theaimsgroup.com/?l=linux-scsi&m=113916262109180&w=2
>
> And see if that would suit your purpose without any additions to
> scsi_command (probably the data carried would have to be the actual
> command).
>
Yeah it looks that will work for the work struct and scsi_host pointer
we were adding. Thanks. Will convert our code.
next prev parent reply other threads:[~2006-02-06 18:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 2:58 [PATCH RFC 1/3] SCSI Userspace Target: scsi-ml changes Mike Christie
2006-02-05 18:30 ` James Bottomley
2006-02-06 2:33 ` FUJITA Tomonori
2006-02-06 17:54 ` Mike Christie
2006-02-06 18:02 ` James Bottomley
2006-02-06 18:22 ` Mike Christie
2006-02-06 18:30 ` Mike Christie
2006-02-06 18:33 ` James Bottomley
2006-02-06 18:45 ` Mike Christie [this message]
2006-02-06 22:14 ` James Bottomley
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=43E79948.2090004@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=James.Bottomley@SteelEye.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--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 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.