From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Ethan Zhao <ethan.zhao@oracle.com>,
jesse.brandeburg@intel.com, shannon.nelson@intel.com,
carolyn.wyborny@intel.com, donald.c.skidmore@intel.com,
bruce.w.allan@intel.com, john.ronciak@intel.com,
mitch.a.williams@intel.com, intel-wired-lan@lists.osuosl.org,
netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, ethan.kernel@gmail.com
Subject: Re: [PATCH] ixgbe: take online CPU number as MQ max limit when alloc_etherdev_mq()
Date: Mon, 16 May 2016 13:58:42 -0700 [thread overview]
Message-ID: <1463432322.2609.12.camel@intel.com> (raw)
In-Reply-To: <1463118995-31763-1-git-send-email-ethan.zhao@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 575 bytes --]
On Fri, 2016-05-13 at 14:56 +0900, Ethan Zhao wrote:
> Allocating 64 Tx/Rx as default doesn't benefit perfomrnace when less
> CPUs were assigned. especially when DCB is enabled, so we should take
> num_online_cpus() as top limit, and aslo to make sure every TC has
> at least one queue, take the MAX_TRAFFIC_CLASS as bottom limit of queues
> number.
>
> Signed-off-by: Ethan Zhao <ethan.zhao@oracle.com>
> ---
> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 4 ++++
> 1 file changed, 4 insertions(+)
Dropping this patch based on Alex's and John's feedback.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Ethan Zhao <ethan.zhao@oracle.com>,
jesse.brandeburg@intel.com, shannon.nelson@intel.com,
carolyn.wyborny@intel.com, donald.c.skidmore@intel.com,
bruce.w.allan@intel.com, john.ronciak@intel.com,
mitch.a.williams@intel.com, intel-wired-lan@lists.osuosl.org,
netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, ethan.kernel@gmail.com
Subject: Re: [PATCH] ixgbe: take online CPU number as MQ max limit when alloc_etherdev_mq()
Date: Mon, 16 May 2016 13:58:42 -0700 [thread overview]
Message-ID: <1463432322.2609.12.camel@intel.com> (raw)
In-Reply-To: <1463118995-31763-1-git-send-email-ethan.zhao@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 575 bytes --]
On Fri, 2016-05-13 at 14:56 +0900, Ethan Zhao wrote:
> Allocating 64 Tx/Rx as default doesn't benefit perfomrnace when less
> CPUs were assigned. especially when DCB is enabled, so we should take
> num_online_cpus() as top limit, and aslo to make sure every TC has
> at least one queue, take the MAX_TRAFFIC_CLASS as bottom limit of queues
> number.
>
> Signed-off-by: Ethan Zhao <ethan.zhao@oracle.com>
> ---
> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 4 ++++
> 1 file changed, 4 insertions(+)
Dropping this patch based on Alex's and John's feedback.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH] ixgbe: take online CPU number as MQ max limit when alloc_etherdev_mq()
Date: Mon, 16 May 2016 13:58:42 -0700 [thread overview]
Message-ID: <1463432322.2609.12.camel@intel.com> (raw)
In-Reply-To: <1463118995-31763-1-git-send-email-ethan.zhao@oracle.com>
On Fri, 2016-05-13 at 14:56 +0900, Ethan Zhao wrote:
> Allocating 64 Tx/Rx as default doesn't benefit perfomrnace when less
> CPUs were assigned. especially when DCB is enabled, so we should take
> num_online_cpus() as top limit, and aslo to make sure every TC has
> at least one queue, take the MAX_TRAFFIC_CLASS as bottom limit of queues
> number.
>
> Signed-off-by: Ethan Zhao <ethan.zhao@oracle.com>
> ---
> ?drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 4 ++++
> ?1 file changed, 4 insertions(+)
Dropping this patch based on Alex's and John's feedback.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20160516/5382db22/attachment.asc>
next prev parent reply other threads:[~2016-05-16 20:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 5:56 [PATCH] ixgbe: take online CPU number as MQ max limit when alloc_etherdev_mq() Ethan Zhao
2016-05-13 5:56 ` [Intel-wired-lan] " Ethan Zhao
2016-05-13 12:52 ` Sergei Shtylyov
2016-05-13 12:52 ` [Intel-wired-lan] " Sergei Shtylyov
2016-05-16 5:38 ` ethan zhao
2016-05-16 5:38 ` [Intel-wired-lan] " ethan zhao
2016-05-13 16:46 ` Alexander Duyck
2016-05-13 16:46 ` [Intel-wired-lan] " Alexander Duyck
2016-05-16 2:59 ` ethan zhao
2016-05-16 2:59 ` [Intel-wired-lan] " ethan zhao
2016-05-16 16:09 ` Alexander Duyck
2016-05-16 16:09 ` [Intel-wired-lan] " Alexander Duyck
2016-05-16 17:14 ` John Fastabend
2016-05-16 17:14 ` John Fastabend
2016-05-17 9:00 ` ethan zhao
2016-05-17 9:00 ` [Intel-wired-lan] " ethan zhao
2016-05-17 15:58 ` Alexander Duyck
2016-05-17 15:58 ` [Intel-wired-lan] " Alexander Duyck
2016-05-16 20:58 ` Jeff Kirsher [this message]
2016-05-16 20:58 ` Jeff Kirsher
2016-05-16 20:58 ` Jeff Kirsher
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=1463432322.2609.12.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=carolyn.wyborny@intel.com \
--cc=donald.c.skidmore@intel.com \
--cc=ethan.kernel@gmail.com \
--cc=ethan.zhao@oracle.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mitch.a.williams@intel.com \
--cc=netdev@vger.kernel.org \
--cc=shannon.nelson@intel.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 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.