From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: announce@dpdk.org
Cc: adrien.mazarguil@6wind.com
Subject: [dpdk-announce] IMPORTANT discussion about Rx filtering API
Date: Wed, 20 Jul 2016 12:28:31 +0200 [thread overview]
Message-ID: <7425690.vJqMrnvbK3@xps13> (raw)
Hi,
There is a proposal in progress to totally rework the configuration
of Rx filtering (including flow director, RSS, etc):
http://dpdk.org/ml/archives/dev/2016-July/043365.html
The target is to integrate this API in 16.11 and migrate the drivers
as fast as possible.
There were some good comments already but only from people interested
in Cavium, Mellanox and Intel devices.
Please developers and maintainers from Amazon, Broadcom, Chelsio, Cisco,
Netronome, QLogic and others, we are waiting your feedbacks.
The intent is to be as generic as possible. But if unfortunately this
new API do not interface well with the hardware you care of, it will
be really harder to fix it later.
Last question: can you commit to migrate your driver in the 16.11
or 17.02 timeframe?
Please answer in the original thread, not this one. This is only
an announce to get more attention on the thread
"Generic flow director/filtering/classification API"
reply other threads:[~2016-07-20 10:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7425690.vJqMrnvbK3@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=adrien.mazarguil@6wind.com \
--cc=announce@dpdk.org \
/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).