DPDK usage discussions
 help / color / mirror / Atom feed
From: Muhammad Zain-ul-Abideen <zain2294@gmail.com>
To: FQ Liu <qleex001@gmail.com>
Cc: users@dpdk.org, Nishant Verma <vnish11@gmail.com>
Subject: Re: [dpdk-users] How to use more rx queues than RSS queue limit for ixgbe
Date: Wed, 17 Aug 2016 19:40:29 +0500	[thread overview]
Message-ID: <CAN7yQ2p435hh49R9v2uBJgKgP_5d9a-kjgLjXFGQthtxi5iXow@mail.gmail.com> (raw)
In-Reply-To: <CAG7SzU69fJTTf2k6hzSAM4cM6obh0-kunQc2=39sOnX4Mhdhag@mail.gmail.com>

Doesn't 82599 has like 128 RX queues

On 17 Aug 2016 12:38 p.m., "FQ Liu" <qleex001@gmail.com> wrote:
>
> Hi
>
> In production environment, all the packets have the same dst_ip, dst_port
> and protocol, I cannot use vlan tag to identity in DCB mode.
> If use Flow Director, one filter rule would direct to only one core,
> Maybe I must modify the driver source code to meet the demand?
>
> 2016-08-16 21:35 GMT+08:00 Nishant Verma <vnish11@gmail.com>:
>
> > Hi,
> >
> > Yes, you can use flow director and other packet classification methods
> > present, the thing is your hardware supports that. Check NIC datasheet
if
> > some thing you think is correct and still not working.
> > For DCB, you can check example(vmdq_dcb) present in example folder in
DPDK.
> > For Flow Director, you can check test-pmd code.
> >
> > Just for your information. flow director can be used like this
> > "
> >     struct rte_eth_fdir_filter entry;
> >
> >     memset(&entry, 0, sizeof(struct rte_eth_fdir_filter));
> >
> >     entry.input.flow_type = 0x05;
> >     entry.input.flow.udp4_flow.ip.dst_ip=0x11223344;
> >     entry.input.flow.udp4_flow.dst_port=0x1111;
> >     entry.action.rx_queue=0x02;
> >     entry.action.report_status=0x02;
> >
> >     ret = rte_eth_dev_filter_ctrl(0, RTE_ETH_FILTER_FDIR,
> >                          RTE_ETH_FILTER_ADD, &entry);
> >
> > "
> > So, from now packet received from 0x11223344 will be re-directed to
queue
> > 2.
> >
> >
> > On Tue, Aug 16, 2016 at 6:25 AM, FQ Liu <qleex001@gmail.com> wrote:
> >
> >> Hi all
> >>       I want to use 32 cores to process dns requests, which would need
32
> >> rx queues, but the maximum RSS queue of the ethernet controller(Intel
> >> Corporation 82599ES 10-Gigabit SFI/SFP+) is 16. If I can use dcb or
flow
> >> director to assign requests to 32 cores?
> >>        The document (http://dpdk.org/doc/guides/nics/overview.html)
shows
> >> that ixgbe driver supports DCB and Flow director, but there isn't any
> >> details about.
> >>
> >>
> >>        OS: centos
> >>        kernel: linux-3.18.34
> >>        driver: igb_uio
> >>
> >
> >
> >
> > --
> > Rgds,
> > Nishant
> >
> >
> >
> >

  parent reply	other threads:[~2016-08-17 14:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-16 10:25 FQ Liu
2016-08-16 13:35 ` Nishant Verma
     [not found]   ` <CAG7SzU69fJTTf2k6hzSAM4cM6obh0-kunQc2=39sOnX4Mhdhag@mail.gmail.com>
2016-08-17 14:40     ` Muhammad Zain-ul-Abideen [this message]
2016-08-17 19:49       ` dave seddon
2016-08-18 12:32         ` Muhammad Zain-ul-Abideen

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=CAN7yQ2p435hh49R9v2uBJgKgP_5d9a-kjgLjXFGQthtxi5iXow@mail.gmail.com \
    --to=zain2294@gmail.com \
    --cc=qleex001@gmail.com \
    --cc=users@dpdk.org \
    --cc=vnish11@gmail.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).