From: David Miller <davem@davemloft.net>
To: alexander.h.duyck@intel.com
Cc: netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
john.r.fastabend@intel.com, tom@herbertland.com
Subject: Re: [net-next PATCH v2 0/4] Add support for XPS when using DCB
Date: Mon, 31 Oct 2016 15:01:05 -0400 (EDT) [thread overview]
Message-ID: <20161031.150105.1254982711155992939.davem@davemloft.net> (raw)
In-Reply-To: <20161028154126.67826.76735.stgit@ahduyck-blue-test.jf.intel.com>
From: Alexander Duyck <alexander.h.duyck@intel.com>
Date: Fri, 28 Oct 2016 11:42:45 -0400
> This patch series enables proper isolation between traffic classes when
> using XPS while DCB is enabled. Previously enabling XPS would cause the
> traffic to be potentially pulled from one traffic class into another on
> egress. This change essentially multiplies the XPS map by the number of
> traffic classes and allows us to do a lookup per traffic class for a given
> CPU.
>
> To guarantee the isolation I invalidate the XPS map for any queues that are
> moved from one traffic class to another, or if we change the number of
> traffic classes.
>
> v2: Added sysfs to display traffic class
> Replaced do/while with for loop
> Cleaned up several other for for loops throughout the patch
Series applied, thanks Alex.
prev parent reply other threads:[~2016-10-31 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 15:42 [net-next PATCH v2 0/4] Add support for XPS when using DCB Alexander Duyck
2016-10-28 15:43 ` [net-next PATCH v2 1/4] net: Move functions for configuring traffic classes out of inline headers Alexander Duyck
2016-10-28 15:43 ` [net-next PATCH v2 2/4] net: Add sysfs value to determine queue traffic class Alexander Duyck
2016-10-28 15:46 ` [net-next PATCH v2 3/4] net: Refactor removal of queues from XPS map and apply on num_tc changes Alexander Duyck
2016-10-28 15:50 ` [net-next PATCH v2 4/4] net: Add support for XPS with QoS via traffic classes Alexander Duyck
2016-10-31 19:01 ` David Miller [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=20161031.150105.1254982711155992939.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexander.h.duyck@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=tom@herbertland.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).