From: "Liu, Yong" <yong.liu@intel.com>
To: "Peng, Yuan" <yuan.peng@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Peng, Yuan" <yuan.peng@intel.com>
Subject: Re: [dts] [PATCH v2] test_plans: add test plan of queue region
Date: Mon, 6 Nov 2017 01:24:24 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E62F10942@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1508920109-19740-1-git-send-email-yuan.peng@intel.com>
Yuan, one comment below.
Thanks,
Marvin
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of peng,yuan
> Sent: Wednesday, October 25, 2017 4:28 PM
> To: dts@dpdk.org
> Cc: Peng, Yuan <yuan.peng@intel.com>
> Subject: [dts] [PATCH v2] test_plans: add test plan of queue region
>
> From: Peng Yuan <yuan.peng@intel.com>
>
> Signed-off-by: Peng Yuan <yuan.peng@intel.com>
>
> +
> +FVL/FPK and future CVL/CPK NICs support queue regions configuration for
> +RSS in PF/VF, so different traffic classes or different packet
> +classification types can be separated to different queues.
> +
This mean traffic classes and packet classification can co-existing with the support of queue region functionality?
Please change the description words, let users known the benefit of this feature.
> +Examples:
> +
> +• all TCP packets with SYN flags set can be sent to queue A, when TCP
> + packets with out SYN flags will be distributed to queues B-F.
> +
> +• IPv4 and IPv6 packets distributed to different queue regions
> +
> +• UDP and TCP packets distributed to different queue regions
> +
> +• Different tunnels distributed to different queue regions (requires
> + tunnels PCTYPEs creation using personalization profiles)
> +
> +• different traffic classes defined in VLAN PCP bits distributed to
> + different queue regions
> +
prev parent reply other threads:[~2017-11-06 1:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 8:28 peng,yuan
2017-11-06 1:24 ` Liu, Yong [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=86228AFD5BCD8E4EBFD2B90117B5E81E62F10942@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=dts@dpdk.org \
--cc=yuan.peng@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).