From: Hannes Reinecke <hare@suse.de>
To: "K. Y. Srinivasan" <kys@microsoft.com>,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, ohering@suse.com,
jbottomley@parallels.com, hch@infradead.org,
linux-scsi@vger.kernel.org, apw@canonical.com,
vkuznets@redhat.com, jasowang@redhat.com,
martin.petersen@oracle.com
Subject: Re: [PATCH V3 4/4] scsi: storvsc: Tighten up the interrupt path
Date: Fri, 18 Dec 2015 09:51:55 +0100 [thread overview]
Message-ID: <5673C92B.5070602@suse.de> (raw)
In-Reply-To: <1450038512-19252-4-git-send-email-kys@microsoft.com>
On 12/13/2015 09:28 PM, K. Y. Srinivasan wrote:
> On the interrupt path, we repeatedly establish the pointer to the
> storvsc_device. Fix this.
>
> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> Reviewed-by: Long Li <longli@microsoft.com>
> Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de>
> Tested-by: Alex Ng <alexng@microsoft.com>
> ---
> drivers/scsi/storvsc_drv.c | 23 ++++++++---------------
> 1 files changed, 8 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/scsi/storvsc_drv.c b/drivers/scsi/storvsc_drv.c
> index d6ca4f2..b68aebe 100644
> --- a/drivers/scsi/storvsc_drv.c
> +++ b/drivers/scsi/storvsc_drv.c
> @@ -945,19 +945,16 @@ static void storvsc_handle_error(struct vmscsi_request *vm_srb,
> }
>
>
> -static void storvsc_command_completion(struct storvsc_cmd_request *cmd_request)
> +static void storvsc_command_completion(struct storvsc_cmd_request *cmd_request,
> + struct storvsc_device *stor_dev)
> {
> struct scsi_cmnd *scmnd = cmd_request->cmd;
> - struct hv_host_device *host_dev = shost_priv(scmnd->device->host);
> struct scsi_sense_hdr sense_hdr;
> struct vmscsi_request *vm_srb;
> struct Scsi_Host *host;
> - struct storvsc_device *stor_dev;
> - struct hv_device *dev = host_dev->dev;
> u32 payload_sz = cmd_request->payload_sz;
> void *payload = cmd_request->payload;
>
> - stor_dev = get_in_stor_device(dev);
> host = stor_dev->host;
>
> vm_srb = &cmd_request->vstor_packet.vm_srb;
> @@ -987,14 +984,13 @@ static void storvsc_command_completion(struct storvsc_cmd_request *cmd_request)
> kfree(payload);
> }
>
> -static void storvsc_on_io_completion(struct hv_device *device,
> +static void storvsc_on_io_completion(struct storvsc_device *stor_device,
> struct vstor_packet *vstor_packet,
> struct storvsc_cmd_request *request)
> {
> - struct storvsc_device *stor_device;
> struct vstor_packet *stor_pkt;
> + struct hv_device *device = stor_device->device;
>
> - stor_device = hv_get_drvdata(device);
> stor_pkt = &request->vstor_packet;
>
> /*
> @@ -1049,7 +1045,7 @@ static void storvsc_on_io_completion(struct hv_device *device,
> stor_pkt->vm_srb.data_transfer_length =
> vstor_packet->vm_srb.data_transfer_length;
>
> - storvsc_command_completion(request);
> + storvsc_command_completion(request, stor_device);
>
> if (atomic_dec_and_test(&stor_device->num_outstanding_req) &&
> stor_device->drain_notify)
> @@ -1058,21 +1054,19 @@ static void storvsc_on_io_completion(struct hv_device *device,
>
> }
>
> -static void storvsc_on_receive(struct hv_device *device,
> +static void storvsc_on_receive(struct storvsc_device *stor_device,
> struct vstor_packet *vstor_packet,
> struct storvsc_cmd_request *request)
> {
> struct storvsc_scan_work *work;
> - struct storvsc_device *stor_device;
>
> switch (vstor_packet->operation) {
> case VSTOR_OPERATION_COMPLETE_IO:
> - storvsc_on_io_completion(device, vstor_packet, request);
> + storvsc_on_io_completion(stor_device, vstor_packet, request);
> break;
>
> case VSTOR_OPERATION_REMOVE_DEVICE:
> case VSTOR_OPERATION_ENUMERATE_BUS:
> - stor_device = get_in_stor_device(device);
> work = kmalloc(sizeof(struct storvsc_scan_work), GFP_ATOMIC);
> if (!work)
> return;
> @@ -1083,7 +1077,6 @@ static void storvsc_on_receive(struct hv_device *device,
> break;
>
> case VSTOR_OPERATION_FCHBA_DATA:
> - stor_device = get_in_stor_device(device);
> cache_wwn(stor_device, vstor_packet);
> #ifdef CONFIG_SCSI_FC_ATTRS
> fc_host_node_name(stor_device->host) = stor_device->node_name;
> @@ -1133,7 +1126,7 @@ static void storvsc_on_channel_callback(void *context)
> vmscsi_size_delta));
> complete(&request->wait_event);
> } else {
> - storvsc_on_receive(device,
> + storvsc_on_receive(stor_device,
> (struct vstor_packet *)packet,
> request);
> }
>
Hmm. I would've thought the compiler optimizes this away. Have you
checked whether it actually makes a difference in the assembler output?
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2015-12-18 8:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-13 20:28 [PATCH V3 0/4] scsi: storvsc: Properly support FC hosts K. Y. Srinivasan
2015-12-13 20:28 ` [PATCH V3 1/4] scsi: storvsc: Fix a bug in the layout of the hv_fc_wwn_packet K. Y. Srinivasan
2015-12-13 20:28 ` [PATCH V3 2/4] scsi: storvsc: Properly support Fibre Channel devices K. Y. Srinivasan
2015-12-18 8:49 ` Hannes Reinecke
2015-12-18 17:13 ` KY Srinivasan
2015-12-18 17:13 ` James Bottomley
2015-12-21 16:02 ` KY Srinivasan
2015-12-13 20:28 ` [PATCH V3 3/4] scsi: storvsc: Refactor the code in storvsc_channel_init() K. Y. Srinivasan
2015-12-18 8:50 ` Hannes Reinecke
2015-12-13 20:28 ` [PATCH V3 4/4] scsi: storvsc: Tighten up the interrupt path K. Y. Srinivasan
2015-12-18 8:51 ` Hannes Reinecke [this message]
2015-12-18 16:20 ` KY Srinivasan
2015-12-18 16:48 ` James Bottomley
2015-12-19 2:28 ` KY Srinivasan
2015-12-21 7:42 ` Hannes Reinecke
2015-12-21 16:28 ` James Bottomley
2015-12-21 19:40 ` KY Srinivasan
2015-12-18 8:40 ` [PATCH V3 1/4] scsi: storvsc: Fix a bug in the layout of the hv_fc_wwn_packet Hannes Reinecke
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=5673C92B.5070602@suse.de \
--to=hare@suse.de \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=jasowang@redhat.com \
--cc=jbottomley@parallels.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ohering@suse.com \
--cc=vkuznets@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).