From: Hannes Reinecke <hare@suse.de>
To: Viswas.G@microchip.com, john.garry@huawei.com,
jejb@linux.ibm.com, martin.petersen@oracle.com,
akshatzen@google.com, Ruksar.devadi@microchip.com,
radha@google.com, bjashnani@google.com, vishakhavc@google.com,
jinpu.wang@cloud.ionos.com, Ashokkumar.N@microchip.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
kashyap.desai@broadcom.com, ming.lei@redhat.com
Subject: Re: [RFC/RFT PATCH] scsi: pm8001: Expose HW queues for pm80xx hw
Date: Tue, 16 Feb 2021 19:15:44 +0100 [thread overview]
Message-ID: <23f6201d-130a-5bf3-c828-c06f0e0acfbe@suse.de> (raw)
In-Reply-To: <SN6PR11MB3488932892D5F34FEE6984499D889@SN6PR11MB3488.namprd11.prod.outlook.com>
On 2/15/21 6:31 PM, Viswas.G@microchip.com wrote:
> Hi John,
>
> We could test this patch and it works fine. Regarding the usage of request->tag, We have some challenges there.
> Pm80xx driver need tag for internal command as well. Tag is controller wide and we need to assign unique tag
> for internal command as well. If we use request->tag, how can we get tag for internal commands ? If driver
> allocate that, how can we make sure it will not conflict with the request->tag ?
>
I have posted a patchset for internal tags some time ago; at the time it
was blocked by the missing shared tagset functionality.
But seeing that we're having it now I guess I'll need to repost; that
addresses precisely the issue you've described.
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
prev parent reply other threads:[~2021-02-16 18:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 11:17 John Garry
2021-01-11 11:57 ` Jinpu Wang
2021-01-11 12:05 ` John Garry
2021-01-31 7:19 ` Viswas.G
2021-02-01 11:23 ` John Garry
2021-02-01 17:08 ` Viswas.G
2021-02-01 17:15 ` John Garry
2021-02-02 4:16 ` Viswas.G
2021-02-15 17:31 ` Viswas.G
2021-02-15 18:00 ` John Garry
2021-02-16 18:15 ` Hannes Reinecke [this message]
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=23f6201d-130a-5bf3-c828-c06f0e0acfbe@suse.de \
--to=hare@suse.de \
--cc=Ashokkumar.N@microchip.com \
--cc=Ruksar.devadi@microchip.com \
--cc=Viswas.G@microchip.com \
--cc=akshatzen@google.com \
--cc=bjashnani@google.com \
--cc=jejb@linux.ibm.com \
--cc=jinpu.wang@cloud.ionos.com \
--cc=john.garry@huawei.com \
--cc=kashyap.desai@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=radha@google.com \
--cc=vishakhavc@google.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
all inboxes | Powered by JetHome®