DPDK patches and discussions
 help / color / mirror / Atom feed
From: Alex Forster <alex@alexforster.com>
To: "Zhang, Helin" <helin.zhang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Flow Director Example?
Date: Mon, 2 May 2016 15:28:17 +0000	[thread overview]
Message-ID: <403E9AFF-32F7-4BEE-B78F-F68D7F52DBB8@alexforster.com> (raw)
In-Reply-To: <F35DEAC7BCE34641BA9FAC6BCA4A12E70AA1EE4B@SHSMSX103.ccr.corp.intel.com>

Hi Helin, thanks for the reply.

Some code might help me explain myself better-

port->configuration = rte_eth_conf {
        .fdir_conf = {
                .mode = RTE_FDIR_MODE_SIGNATURE,
                .pballoc = RTE_FDIR_PBALLOC_64K,
                .mask = rte_eth_fdir_masks {
                        .ipv4_mask = rte_eth_ipv4_flow {
                                .dst_ip = 0x0,
                        },
                        .ipv6_mask = rte_eth_ipv6_flow {
                                .dst_ip = { 0x0, 0x0, 0x0, 0x0 },
                        },
                },
                .status = RTE_FDIR_REPORT_STATUS,
                .drop_queue = 127,
        },
        .rxmode = {
                .mq_mode = ETH_MQ_RX_NONE,
                .max_rx_pkt_len = ETHER_MAX_LEN,
                .split_hdr_size = 0,
                .header_split   = 0,
                .hw_ip_checksum = 0,
                .hw_vlan_filter = 0,
                .jumbo_frame    = 0,
                .hw_strip_crc   = 0,
        },
        .txmode = {
                .mq_mode = ETH_MQ_TX_NONE,
        },
};




I'm trying to direct packets with the same destination IPv4 or IPv6 address into the same RX queues. I haven't been able to find any examples of using Flow Director with DPDK, so I'm sure I'm doing something obviously wrong here, but I can't figure out what it is.

Alex Forster

On 5/2/16, 1:38 AM, "Zhang, Helin" <helin.zhang@intel.com> wrote:

>Hi Alex
>
>Can you confirm that you are using DPDK? And how do you use DPDK and possibly kernel driver?
>I need your detailed topo of how are you using DPDK, as I am a bit confused. Thanks!
>
>Regards,
>Helin
>
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Alex Forster
>> Sent: Saturday, April 30, 2016 4:34 AM
>> To: dev@dpdk.org
>> Subject: [dpdk-dev] Flow Director Example?
>> 
>> Hi guys, apologies if this is the wrong list, but the others look pretty bare.
>> 
>> We have a 32 core server that has two X520-QDA1's NICs with 2x10G ports
>> plugged into each. I'm using 2016.1 (latest stable) with ixgbe 4.3.15 (latest stable).
>> I'm setting up 8 RX queues per port, and I'd like Flow Director in signature mode
>> (?) to place packets into queues based on a hash of destination IPv4 or IPv6
>> address. However, I can't figure out rte_fdir_conf, and despite a good amount of
>> trial and error, each of my ports are still only using one of the RX queues I set up.
>> 
>> Would anyone be able to point me in the right direction here? Thanks in advance!
>> 
>> Alex Forster

      reply	other threads:[~2016-05-02 15:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-29 20:34 Alex Forster
2016-05-02  5:38 ` Zhang, Helin
2016-05-02 15:28   ` Alex Forster [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=403E9AFF-32F7-4BEE-B78F-F68D7F52DBB8@alexforster.com \
    --to=alex@alexforster.com \
    --cc=dev@dpdk.org \
    --cc=helin.zhang@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).