All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Kirill Rybalchenko <kirill.rybalchenko@intel.com>
Cc: dev@dpdk.org, jingjing.wu@intel.com, beilei.xing@intel.com,
	johndale@cisco.com, neescoba@cisco.com,
	nelio.laranjeiro@6wind.com, yskoh@mellanox.com,
	wenzhuo.lu@intel.com, konstantin.ananyev@intel.com,
	andrey.chilikin@intel.com
Subject: Re: [PATCH] ethdev: increase flow type limit from 32 to 64
Date: Mon, 4 Dec 2017 18:43:04 +0100	[thread overview]
Message-ID: <20171204174304.GK4062@6wind.com> (raw)
In-Reply-To: <1511785787-127452-1-git-send-email-kirill.rybalchenko@intel.com>

Hi Kirill,

On Mon, Nov 27, 2017 at 12:29:47PM +0000, Kirill Rybalchenko wrote:
> Increase the internal limit for flow types from 32 to 64
> to support future flow type extensions.
> Change type of variables from uint32_t[] to uint64_t[]:
>   rte_eth_fdir_info.flow_types_mask
>   rte_eth_hash_global_conf.sym_hash_enable_mask
>   rte_eth_hash_global_conf.valid_bit_mask
> 
> This modification affects the following components:
>   net/i40e
>   net/enic
>   net/mlx5
>   net/ixgbe
>   app/testpmd
> 
> Signed-off-by: Kirill Rybalchenko <kirill.rybalchenko@intel.com>

Can you elaborate a bit on the need for these changes?
Have you considered implementing those future extensions through rte_flow
instead?

-- 
Adrien Mazarguil
6WIND

  reply	other threads:[~2017-12-04 17:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 12:29 [PATCH] ethdev: increase flow type limit from 32 to 64 Kirill Rybalchenko
2017-12-04 17:43 ` Adrien Mazarguil [this message]
2018-01-09 15:16   ` Rybalchenko, Kirill
2018-01-10 13:50     ` Thomas Monjalon
2018-01-16 11:13     ` Adrien Mazarguil
2018-01-16 17:23       ` Rybalchenko, Kirill
2018-01-16 18:03         ` Adrien Mazarguil
2018-01-09 14:30 ` Zhang, Helin
2018-01-10  6:51 ` Xing, Beilei
2018-01-15 16:58 ` [PATCH v2] " Kirill Rybalchenko
2018-01-15 17:33   ` [PATCH v3] " Kirill Rybalchenko
2018-01-15 21:27     ` Thomas Monjalon
2018-01-16  9:44       ` Rybalchenko, Kirill
2018-01-16  9:47         ` Thomas Monjalon
2018-01-16 10:31           ` Rybalchenko, Kirill
2018-01-16 10:38             ` Thomas Monjalon
2018-01-17 16:56     ` Ferruh Yigit
2018-01-18  9:24       ` Rybalchenko, Kirill
2018-01-18 12:25       ` Ferruh Yigit

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=20171204174304.GK4062@6wind.com \
    --to=adrien.mazarguil@6wind.com \
    --cc=andrey.chilikin@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=johndale@cisco.com \
    --cc=kirill.rybalchenko@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=neescoba@cisco.com \
    --cc=nelio.laranjeiro@6wind.com \
    --cc=wenzhuo.lu@intel.com \
    --cc=yskoh@mellanox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.