DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] RSS API discussion
Date: Fri, 16 Oct 2015 13:40:00 +0000	[thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09090209FB49@shsmsx102.ccr.corp.intel.com> (raw)

Hi Nélio,
 
> Hi Wenzhuo,
> 
> We should discuss about this API for a future release of DPDK because this one
> lacks in flexibility.  Some other NICs have indirection tables with a
> different/configurable size, and the current API does not help to manage it.
> 
> For ConnectX-4 I have made a lot of hacks to avoid changing the DPDK API,
> "[dpdk-dev] [PATCH 0/3] Add RETA configuration to MLX5".
> http://dpdk.org/ml/archives/dev/2015-October/024681.html
> 
> From a user point of view, to update the RETA table, the API expects the user to
> know the size of it to update or query.  With your patchset, Intel have two
> indirection table sizes now, with Mellanox ConnectX-4, I fixed to the size of 512
> entries because it is not fixed by default.
> 
> How about discussing this in a separate thread?
Sure, I changed the tittle.
But I'm afraid I don't catch up with you. I have 2 questions, 1, Why the reta size cannot be predict on  Mellanox ConnectX-4? 2, I don't understand the meaning when you say the reta size is not fixed by default on Mellanox ConnectX-4.
Would you like to give more details of the Mellanox ConnectX-4's behavior? It'll be helpful to understand this problem.

> 
> Regards,
> 
> --
> Nélio Laranjeiro
> 6WIND

             reply	other threads:[~2015-10-16 13:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16 13:40 Lu, Wenzhuo [this message]
2015-10-16 15:28 ` Nélio Laranjeiro
2015-10-19  1:37   ` Lu, Wenzhuo

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=6A0DE07E22DDAD4C9103DF62FEBC09090209FB49@shsmsx102.ccr.corp.intel.com \
    --to=wenzhuo.lu@intel.com \
    --cc=dev@dpdk.org \
    --cc=nelio.laranjeiro@6wind.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).