All of lore.kernel.org
 help / color / mirror / Atom feed
From: FUJITA Tomonori <tomof@acm.org>
To: Eric.Moore@lsi.com
Cc: fujita.tomonori@lab.ntt.co.jp, James.Bottomley@steeleye.com,
	linux-scsi@vger.kernel.org, dougg@torque.net,
	jens.axboe@oracle.com
Subject: RE: [PATCH 3/3] mptsas: add SMP passthrough support via bsg
Date: Fri, 27 Jul 2007 02:28:12 +0900	[thread overview]
Message-ID: <20070726022605N.tomof@acm.org> (raw)
In-Reply-To: <20070726020657P.tomof@acm.org>

From: FUJITA Tomonori <tomof@acm.org>
Subject: RE: [PATCH 3/3] mptsas: add SMP passthrough support via bsg
Date: Fri, 27 Jul 2007 02:09:05 +0900

> Use-space applications can put four memory addresses in the bsg (sg
> v4) interface: request, response, dout_xferp, and din_xferp.
> 
> For scsi commands, we use:
> 
> request -> pointer to a scsi command (cmdp in sgv3)
> response -> pointer to a sense buffer (sbp in sgv3)
> dout_xferp -> pointer to out data
> din_xferp -> pointer to in data
> 
> For smp request/response, we use:
> 
> request -> not used
> response -> not used
> dout_xferp -> pointer to a smp request frame
> din_xferp -> pointer to a smp response frame
> 
> 
> So we could use response field to send vendor's unique response to
> user space.
> 
> bsg wrongly assues the response field is used for sense buffer so the
> maxium length is SCSI_SENSE_BUFFERSIZE, 96 bytes. I think that it's a
> bit small for mpt's unique response. But, I'll fix the length
> limitation bug soon.

Oops, 96 bytes is large enough for mpt's unique response. Right?

  reply	other threads:[~2007-07-26 17:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09  3:52 [PATCH 3/3] mptsas: add SMP passthrough support via bsg FUJITA Tomonori
2007-07-24  0:11 ` Moore, Eric
2007-07-24  5:27   ` FUJITA Tomonori
2007-07-25  0:22     ` Moore, Eric
2007-07-25  0:47       ` FUJITA Tomonori
2007-07-26  0:21         ` Moore, Eric
2007-07-26 10:09           ` FUJITA Tomonori
2007-07-26 16:32             ` Moore, Eric
2007-07-26 17:09               ` FUJITA Tomonori
2007-07-26 17:28                 ` FUJITA Tomonori [this message]
2007-07-26 22:05                 ` Moore, Eric
2007-07-27  0:43                   ` FUJITA Tomonori
2007-07-27 23:24                     ` Moore, Eric
2007-07-29  5:07                       ` FUJITA Tomonori
2007-07-29  7:36                         ` FUJITA Tomonori
2007-07-30 17:10                           ` Moore, Eric
2007-07-30 23:36                             ` FUJITA Tomonori
2007-07-31 15:34                               ` Moore, Eric
2007-07-25  4:33       ` FUJITA Tomonori

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=20070726022605N.tomof@acm.org \
    --to=tomof@acm.org \
    --cc=Eric.Moore@lsi.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=dougg@torque.net \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=jens.axboe@oracle.com \
    --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.