From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next v5 0/4] igb: enable RX network flow classification
Date: Mon, 16 May 2016 15:21:09 -0700 [thread overview]
Message-ID: <1463437269.2609.20.camel@intel.com> (raw)
In-Reply-To: <1462786062-7572-1-git-send-email-gangfeng.huang@ni.com>
On Mon, 2016-05-09 at 17:27 +0800, Gangfeng wrote:
> After apply this series of patches, igb driver will supports advanced
> RX filter that direct receive packets by flows to different hardware
> queue. Enables tight control on routing a flow in the platform.
>
> In our product, we use the the RX traffic classification to gurantee the
> PTP(ethertype is 0x88F7) packets won't be flooded by best effort packet.
> PTP packets is always be processed by Linux network stack.
>
> step 1.?
> ? use the ethertype filter to filter most of packet(0x0800) to HW queue;
> step 2.
> ? Add a rule to forward the PTP packets to another HW queue
>
> The ethtool commands and options:
>
> -n --show-nfc
> ?? Retrieves the receive network flow classification configurations
>
> -N --config-nfc
> ?? Configures the receive network flow classification classification
>
> Change history of this patches:
> Version 1:
> ? Split the patch to 3 patches for review;
> ? Save the filters and restore them after a reset;
> ? In ethtool command, use key word "proto" to replace "vlan-etype:
> ? Fix bugs
> Version 2:
> ? Rebase the patches on the the latest dev-queue;
> Version 3:
> ? Report a meaningful error code for misoperation;
> Version 4:
> ? Rebase the patches on latest dev-queue;
> ? Update the patch description and code comments;?
> Version 5:
> ? Rebase the patches on latest dev-queue;
> ? Update the patch description;
Based on the issues validation has found with your first patch, I am
dropping your series of patches. ?Please address the issues Aaron found
during validation.
-------------- 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/6b7d9e6b/attachment-0001.asc>
prev parent reply other threads:[~2016-05-16 22:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 9:27 [Intel-wired-lan] [PATCH net-next v5 0/4] igb: enable RX network flow classification Gangfeng
2016-05-09 9:27 ` [Intel-wired-lan] [PATCH net-next v5 1/4] igb: add support of " Gangfeng
2016-05-16 22:09 ` Brown, Aaron F
2016-05-17 1:45 ` Brown, Aaron F
2016-06-29 19:12 ` Matt Porter
2016-06-29 20:06 ` Brown, Aaron F
2016-06-30 1:20 ` Brown, Aaron F
2016-06-30 15:28 ` 'Matt Porter'
2016-06-30 16:16 ` 'Matt Porter'
2016-06-30 19:51 ` Brown, Aaron F
2016-06-30 20:10 ` 'Matt Porter'
2016-07-04 3:12 ` Gangfeng Huang
2016-07-06 8:28 ` Gangfeng Huang
2016-07-06 12:29 ` 'Matt Porter'
2016-05-09 9:27 ` [Intel-wired-lan] [PATCH net-next v5 2/4] igb: support RX flow classification by ethertype Gangfeng
2016-05-09 9:27 ` [Intel-wired-lan] [PATCH net-next v5 3/4] igb: support RX flow classification by VLAN priority Gangfeng
2016-05-09 9:27 ` [Intel-wired-lan] [PATCH net-next v5 4/4] igb: fix error code in igb_add_ethtool_nfc_entry() Gangfeng
2016-05-16 22:21 ` Jeff Kirsher [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=1463437269.2609.20.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=intel-wired-lan@osuosl.org \
/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