From: Christoph Hellwig <hch@lst.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Christoph Hellwig <hch@lst.de>,
linux-scsi@vger.kernel.org, axboe@kernel.dk
Subject: Re: [PATCH, RFC] scsi: use host wide tags by default
Date: Sat, 18 Apr 2015 11:05:08 +0200 [thread overview]
Message-ID: <20150418090508.GA31566@lst.de> (raw)
In-Reply-To: <1429306960.1079.25.camel@HansenPartnership.com>
On Fri, Apr 17, 2015 at 02:42:40PM -0700, James Bottomley wrote:
> > if(hostdata->msgin[1] == A_SIMPLE_TAG_MSG) {
> > - struct scsi_cmnd *SCp = scsi_find_tag(SDp, hostdata->msgin[2]);
> > + struct scsi_cmnd *SCp;
> > +
> > + SCp = scsi_find_tag(SDp->host, hostdata->msgin[2]);
>
> This (and the following) is a stylistic modification and doesn't really
> belong here.
Both split lines that would grow beyond 80 lines.
> This lock/unlock is a nasty global sync point which can be eliminated:
> we can rely on the architectural atomicity of 32 bit writes (might need
> to make sdev->queue_depth a u32 because I seem to remember 16 bit writes
> had to be done as two byte stores on some architectures).
It's much more easy to understand than the barrier magic we'd otherwise
have to do, and this is a slow path. Nevermind that it would be an
unrelated change even if we had a good argument for it.
next prev parent reply other threads:[~2015-04-18 9:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 20:11 [PATCH, RFC] scsi: use host wide tags by default Christoph Hellwig
2015-04-17 21:42 ` James Bottomley
2015-04-17 21:44 ` Jens Axboe
2015-04-17 21:46 ` James Bottomley
2015-04-17 21:47 ` Jens Axboe
2015-04-17 21:57 ` James Bottomley
2015-04-17 22:07 ` Jens Axboe
2015-04-17 22:20 ` James Bottomley
2015-04-17 22:40 ` Jens Axboe
2015-04-20 18:07 ` James Bottomley
2015-04-18 4:05 ` Elliott, Robert (Server Storage)
2015-04-18 9:05 ` Christoph Hellwig [this message]
2015-04-17 21:43 ` Jens Axboe
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=20150418090508.GA31566@lst.de \
--to=hch@lst.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=axboe@kernel.dk \
--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.