From: David Marchand <david.marchand@redhat.com>
To: dev <dev@dpdk.org>
Cc: Ferruh Yigit <ferruh.yigit@amd.com>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
"Mcnamara, John" <john.mcnamara@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: flow classify library status
Date: Tue, 25 Oct 2022 16:37:24 +0200 [thread overview]
Message-ID: <CAJFAV8wL1itESOApU9cmhDLP8beNrOt43FxaO7TkCDxcJee8MQ@mail.gmail.com> (raw)
Hello,
The flow_classify library has been out and marked experimental for a long time.
Its current maintainer is now leaving the community.
The library did not get much traction: I am not aware of an opensource
project using it.
Are there users of this library?
If we deprecated it (to later drop it), do we already have some
replacement feature in DPDK?
--
David Marchand
next reply other threads:[~2022-10-25 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 14:37 David Marchand [this message]
2022-10-25 15:24 ` Ferruh Yigit
2022-10-25 22:57 ` Konstantin Ananyev
2022-10-25 15:59 ` Stephen Hemminger
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=CAJFAV8wL1itESOApU9cmhDLP8beNrOt43FxaO7TkCDxcJee8MQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=john.mcnamara@intel.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).