From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: David Miller <davem@davemloft.net>, amritha.nambiar@intel.com
Cc: intel-wired-lan@lists.osuosl.org, alexander.h.duyck@intel.com,
kiran.patil@intel.com, netdev@vger.kernel.org,
mitch.a.williams@intel.com, alexander.duyck@gmail.com,
neerav.parikh@intel.com, sridhar.samudrala@intel.com,
carolyn.wyborny@intel.com
Subject: Re: [PATCH 0/6] Configuring traffic classes via new hardware offload mechanism in tc/mqprio
Date: Tue, 11 Jul 2017 17:18:17 -0700 [thread overview]
Message-ID: <1499818697.4698.12.camel@intel.com> (raw)
In-Reply-To: <20170711.072635.185388451319287053.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 639 bytes --]
On Tue, 2017-07-11 at 07:26 -0700, David Miller wrote:
> From: Amritha Nambiar <amritha.nambiar@intel.com>
> Date: Tue, 11 Jul 2017 03:18:30 -0700
>
> > The following series introduces a new hardware offload mode in
> > tc/mqprio where the TCs, the queue configurations and
> > bandwidth rate limits are offloaded to the hardware.
>
> net-next is closed, please resubmit this when net-next opens
> again:
>
> http://vger.kernel.org/~davem/net-next.html
>
> Thank you.
Dave, this is gonna come through my tree. Amritha is looking for
community feedback, while we have this under validation. Sorry for the
confusion.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-07-12 0:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 10:18 [PATCH 0/6] Configuring traffic classes via new hardware offload mechanism in tc/mqprio Amritha Nambiar
2017-07-11 10:18 ` [PATCH 1/6] [next-queue]net: mqprio: Introduce new hardware offload mode in mqprio for offloading full TC configurations Amritha Nambiar
2017-07-14 8:36 ` Jamal Hadi Salim
2017-07-15 2:00 ` Nambiar, Amritha
2017-07-11 10:18 ` [PATCH 2/6] [next-queue]net: i40e: Add macro for PF reset bit Amritha Nambiar
2017-07-11 10:18 ` [PATCH 3/6] [next-queue]net: i40e: Add infrastructure for queue channel support with the TCs and queue configurations offloaded via mqprio scheduler Amritha Nambiar
2017-07-11 10:18 ` [PATCH 4/6] [next-queue]net: i40e: Enable mqprio full offload mode in the i40e driver for configuring TCs and queue mapping Amritha Nambiar
2017-07-11 10:18 ` [PATCH 5/6] [next-queue]net: i40e: Refactor VF BW rate limiting function to be reused on the PF as well Amritha Nambiar
2017-07-11 22:32 ` [Intel-wired-lan] " kbuild test robot
2017-07-11 10:19 ` [PATCH 6/6] [next-queue]net: i40e: Add support to set max bandwidth rates for TCs offloaded via tc/mqprio Amritha Nambiar
2017-07-12 14:12 ` [Intel-wired-lan] " kbuild test robot
2017-07-11 14:26 ` [PATCH 0/6] Configuring traffic classes via new hardware offload mechanism in tc/mqprio David Miller
2017-07-12 0:18 ` Jeff Kirsher [this message]
2017-07-12 0:36 ` David Miller
2017-07-14 7:56 ` Jamal Hadi Salim
2017-07-14 10:31 ` Nambiar, Amritha
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=1499818697.4698.12.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=alexander.duyck@gmail.com \
--cc=alexander.h.duyck@intel.com \
--cc=amritha.nambiar@intel.com \
--cc=carolyn.wyborny@intel.com \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kiran.patil@intel.com \
--cc=mitch.a.williams@intel.com \
--cc=neerav.parikh@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sridhar.samudrala@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 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).