All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: Christoph Hellwig <hch@infradead.org>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2/3] target: simplify cmd to task mapping
Date: Wed, 17 Nov 2010 17:51:24 -0500	[thread overview]
Message-ID: <20101117225124.GA7073@infradead.org> (raw)
In-Reply-To: <1290033607.31890.71.camel@haakon2.linux-iscsi.org>

On Wed, Nov 17, 2010 at 02:40:07PM -0800, Nicholas A. Bellinger wrote:
> On Wed, 2010-11-17 at 16:38 -0500, Christoph Hellwig wrote:
> > The cmd to task mapping is almost the same for all control CDBs,
> > except for calling different backend methods to do the backed-specific
> > mapping.  Merge the code performing the mapping into a single
> > new transport_map_control_cmd_to_task helper, and kill the
> > transport_map_task callback by simplify calling the backend methods
> > directly for the single task for a control CDB, and hardcoding
> > ->map_task_SG for data CDBs.
> > 
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
> 
> This one looks very reasonable as the extra set of bitwise AND
> instructions is limited to control path code.
> 
> As for the first one, I don't really have a strong preference either
> way, as long as the difference for extra 4 AND instructions for the bulk
> 'fast past' case is really a wash on modern x86_64 silicon..

This one modifies the code touched by the first.  There's one if else
for data vs control path CDBs and then we switch the different types
of control CDBs.

  parent reply	other threads:[~2010-11-17 22:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17 21:38 [PATCH 2/3] target: simplify cmd to task mapping Christoph Hellwig
2010-11-17 22:40 ` Nicholas A. Bellinger
2010-11-17 22:47   ` Nicholas A. Bellinger
2010-11-17 22:51   ` Christoph Hellwig [this message]
2010-11-18  0:41 ` Nicholas A. Bellinger
2010-11-18 12:07 ` Boaz Harrosh
2010-11-22 21:07   ` Christoph Hellwig
2010-11-23  9:52     ` Boaz Harrosh

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=20101117225124.GA7073@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nab@linux-iscsi.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.