From: John Garry <john.g.garry@oracle.com>
To: Karan Tilak Kumar <kartilak@cisco.com>, sebaddel@cisco.com
Cc: arulponn@cisco.com, djhawar@cisco.com, gcboffa@cisco.com,
mkai2@cisco.com, satishkh@cisco.com, jejb@linux.ibm.com,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 00/13] Introduce support for multiqueue (MQ) in fnic
Date: Thu, 2 Nov 2023 09:00:26 +0000 [thread overview]
Message-ID: <4bfe8125-660f-4ac2-0aa6-aa7a5b6df2e9@oracle.com> (raw)
In-Reply-To: <20231027180302.418676-1-kartilak@cisco.com>
On 27/10/2023 19:02, Karan Tilak Kumar wrote:
> The number of IO queues to be used is stored in a configuration file
> by the VIC firmware. The fNIC driver reads the configuration file and sets
> the number of queues to be used. Previously, the driver was hard-coded
> to use only one queue.
In looking at commit aec95e3a8ded ("scsi: fnic: Refactor code in fnic
probe to initialize SCSI layer"), support to set shost->nr_hw_queues > 1
to enable MQ seems to have sneaked in already - what's going on there?
John
next prev parent reply other threads:[~2023-11-02 9:00 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 18:02 [PATCH v2 00/13] Introduce support for multiqueue (MQ) in fnic Karan Tilak Kumar
2023-10-27 18:02 ` [PATCH v2 01/13] scsi: fnic: Modify definitions to sync with VIC firmware Karan Tilak Kumar
2023-11-02 7:23 ` Hannes Reinecke
2023-11-06 19:47 ` Karan Tilak Kumar (kartilak)
2023-10-27 18:02 ` [PATCH v2 02/13] scsi: fnic: Add and use fnic number Karan Tilak Kumar
2023-11-02 7:25 ` Hannes Reinecke
2023-11-06 19:49 ` Karan Tilak Kumar (kartilak)
2023-10-27 18:02 ` [PATCH v2 03/13] scsi: fnic: Add and improve log messages Karan Tilak Kumar
2023-11-02 7:27 ` Hannes Reinecke
2023-11-06 19:55 ` Karan Tilak Kumar (kartilak)
2023-11-07 7:20 ` Hannes Reinecke
2023-11-07 19:54 ` Karan Tilak Kumar (kartilak)
2023-10-27 18:02 ` [PATCH v2 04/13] scsi: fnic: Rename wq_copy to hw_copy_wq Karan Tilak Kumar
2023-11-02 7:28 ` Hannes Reinecke
2023-11-06 19:57 ` Karan Tilak Kumar (kartilak)
2023-10-27 18:02 ` [PATCH v2 05/13] scsi: fnic: Get copy workqueue count and interrupt mode from config Karan Tilak Kumar
2023-11-02 7:29 ` Hannes Reinecke
2023-11-06 19:59 ` Karan Tilak Kumar (kartilak)
2023-10-27 18:02 ` [PATCH v2 06/13] scsi: fnic: Refactor and redefine fnic.h for multiqueue Karan Tilak Kumar
2023-11-02 7:36 ` Hannes Reinecke
2023-11-06 20:11 ` Karan Tilak Kumar (kartilak)
2023-10-27 18:02 ` [PATCH v2 07/13] scsi: fnic: Modify ISRs to support multiqueue(MQ) Karan Tilak Kumar
2023-11-02 7:45 ` Hannes Reinecke
2023-11-06 20:13 ` Karan Tilak Kumar (kartilak)
2023-10-27 18:02 ` [PATCH v2 08/13] scsi: fnic: Define stats to track multiqueue (MQ) IOs Karan Tilak Kumar
2023-11-02 7:46 ` Hannes Reinecke
2023-10-27 18:02 ` [PATCH v2 09/13] scsi: fnic: Remove usage of host_lock Karan Tilak Kumar
2023-11-02 7:52 ` Hannes Reinecke
2023-11-06 20:20 ` Karan Tilak Kumar (kartilak)
2023-10-27 18:02 ` [PATCH v2 10/13] scsi: fnic: Add support for multiqueue (MQ) in fnic_main.c Karan Tilak Kumar
2023-11-02 7:57 ` Hannes Reinecke
2023-10-27 18:03 ` [PATCH v2 11/13] scsi: fnic: Use fnic_lock to protect fnic structures in queuecommand Karan Tilak Kumar
2023-11-02 8:02 ` Hannes Reinecke
2023-10-27 18:03 ` [PATCH v2 12/13] scsi: fnic: Add support for multiqueue (MQ) in fnic driver Karan Tilak Kumar
2023-10-29 17:20 ` kernel test robot
2023-11-02 8:11 ` Hannes Reinecke
2023-11-06 20:25 ` Karan Tilak Kumar (kartilak)
2023-10-27 18:03 ` [PATCH v2 13/13] scsi: fnic: Improve logs and add support for multiqueue (MQ) Karan Tilak Kumar
2023-11-02 7:59 ` Hannes Reinecke
2023-11-06 20:44 ` Karan Tilak Kumar (kartilak)
2023-11-07 7:27 ` Hannes Reinecke
2023-11-07 18:41 ` Karan Tilak Kumar (kartilak)
2023-11-02 8:14 ` Hannes Reinecke
2023-11-06 20:30 ` Karan Tilak Kumar (kartilak)
2023-11-02 9:00 ` John Garry [this message]
2023-11-06 19:44 ` [PATCH v2 00/13] Introduce support for multiqueue (MQ) in fnic Karan Tilak Kumar (kartilak)
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=4bfe8125-660f-4ac2-0aa6-aa7a5b6df2e9@oracle.com \
--to=john.g.garry@oracle.com \
--cc=arulponn@cisco.com \
--cc=djhawar@cisco.com \
--cc=gcboffa@cisco.com \
--cc=jejb@linux.ibm.com \
--cc=kartilak@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mkai2@cisco.com \
--cc=satishkh@cisco.com \
--cc=sebaddel@cisco.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