DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ori Kam <orika@mellanox.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>,
	"Wei Hu (Xavier)" <xavier.huwei@huawei.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "huwei87@hisilicon.com" <huwei87@hisilicon.com>,
	"fengchengwen@huawei.com" <fengchengwen@huawei.com>
Subject: Re: [dpdk-dev] [RFC PATCH] ethdev: add a new flow action of queue range
Date: Sun, 19 Jul 2020 13:32:42 +0000	[thread overview]
Message-ID: <AM6PR05MB5176F94D04963D071AAA6FCDDB7A0@AM6PR05MB5176.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <996c7d92-6f87-d14a-f084-50372434e01a@solarflare.com>



> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Andrew Rybchenko
> 
> On 7/17/20 12:32 PM, Wei Hu (Xavier) wrote:
> > From: Chengwen Feng <fengchengwen@huawei.com>
> >
> > This patch adds a new flow action of queue range, which was used to assign
> > packets to a continuous queue range.
> >
> > Current FD (flow director) provide a useful means to assign packets to
> > a target queue. But it has the following shortage: it can only route
> > to one queue, and there is an upper limit on one queue rxtx capacity,
> > which means the FD rule need more accurate else it may exceed the
> > queue capacity.
> >
> > With the support of queue range action, user can create FD rule with
> > action routed to a continuous queues, like:
> > 	FD rule 0 ------|-----> queue 0
> > 			|-----> queue 1
> >
> > 	FD rule 1 ------|-----> queue 8
> > 			|-----> queue 9
> > 			|-----> queue 10
> > 			|-----> queue 11
> > Note: hardware can use RSS to distribute traffic to the continuous queues
> > when packets match the above FD rule.
> >
> > With the support of queue range action, we can further provide QoS
> > service when DCB disabled.
> > eg: one NE (network element) is configured with two ip addresses, one for
> > control plane and the other for data plane, user can create two FD rules,
> > the first for directing control plane packets to queue 0, the second for
> > directing data plane packets to queue 1~15.
> 
> I don't understand why it is not covered by RSS action.
> 
+1
This should be covered in RSS action.

> >
> > Signed-off-by: Chengwen Feng <fengchengwen@huawei.com>
> > Signed-off-by: Wei Hu (Xavier) <xavier.huwei@huawei.com>
> 
> [snip]

Best,
Ori

  reply	other threads:[~2020-07-19 13:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17  9:32 Wei Hu (Xavier)
2020-07-19 12:30 ` Andrew Rybchenko
2020-07-19 13:32   ` Ori Kam [this message]
2020-07-19 13:34     ` Ori Kam

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=AM6PR05MB5176F94D04963D071AAA6FCDDB7A0@AM6PR05MB5176.eurprd05.prod.outlook.com \
    --to=orika@mellanox.com \
    --cc=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=huwei87@hisilicon.com \
    --cc=xavier.huwei@huawei.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).