DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jasvinder Singh <jasvinder.singh@intel.com>
Cc: dev@dpdk.org, cristian.dumitrescu@intel.com
Subject: Re: [dpdk-dev] [PATCH v3] ip_pipeline: add rss support
Date: Wed, 08 Jun 2016 20:07:47 +0200	[thread overview]
Message-ID: <5983999.B4X949CiMm@xps13> (raw)
In-Reply-To: <1464628489-81609-1-git-send-email-jasvinder.singh@intel.com>

2016-05-30 18:14, Jasvinder Singh:
> This patch enables rss (receive side scaling) per network interface
> through the configuration file. The user can specify following
> parameters in LINK section for enabling the rss feature - rss_qs,
> rss_proto_ipv4, rss_proto_ipv6 and ip_proto_l2.
> 
> The "rss_qs" is mandatory parameter which indicates the queues to be
> used for rss, while rest of the parameters are optional. When optional
> parameters are not provided in the configuration file, default setting
> (ETH_RSS_IPV4 | ETH_RSS_IPV6) is assumed for "rss_hf" field of the
> rss_conf structure.
> 
> For example, following configuration can be applied for using the rss
> on port 0 of the network interface;
> 
> [PIPELINE0]
> type = MASTER
> core = 0
> 
> [LINK0]
> rss_qs = 0 1
> 
> [PIPELINE1]
> type = PASS-THROUGH
> core = 1
> pktq_in = RXQ0.0 RXQ0.1 RXQ1.0
> pktq_out = TXQ0.0 TXQ1.0 TXQ0.1
> 
> Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>

Applied, thanks

      reply	other threads:[~2016-06-08 18:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-29  9:33 [dpdk-dev] [PATCH] " Jasvinder Singh
2016-05-11 16:31 ` [dpdk-dev] [PATCH v2] " Jasvinder Singh
2016-05-30 17:14   ` [dpdk-dev] [PATCH v3] " Jasvinder Singh
2016-06-08 18:07     ` Thomas Monjalon [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=5983999.B4X949CiMm@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=jasvinder.singh@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).