DPDK patches and discussions
 help / color / mirror / Atom feed
From: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
To: Ferruh Yigit <ferruh.yigit@amd.com>,
	David Marchand <david.marchand@redhat.com>, dev <dev@dpdk.org>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
	Bruce Richardson <bruce.richardson@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: flow classify library status
Date: Tue, 25 Oct 2022 23:57:11 +0100	[thread overview]
Message-ID: <c2a8539a-3e50-e49b-abbd-97705806b7f9@yandex.ru> (raw)
In-Reply-To: <e0b3e001-30cd-388f-33df-8760fc8ab1de@amd.com>

25/10/2022 16:24, Ferruh Yigit пишет:
> On 10/25/2022 3:37 PM, David Marchand wrote:
>> 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?
> 
> +1 to remove it.
> 
> As far as I remember initially it started as underlying work to provide 
> stats with common standards like IPFIX.
> But not sure if next stage ever happened.

Yep, it didn't work.
Agree to deprecate/remove.

  reply	other threads:[~2022-10-25 22:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25 14:37 David Marchand
2022-10-25 15:24 ` Ferruh Yigit
2022-10-25 22:57   ` Konstantin Ananyev [this message]
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=c2a8539a-3e50-e49b-abbd-97705806b7f9@yandex.ru \
    --to=konstantin.v.ananyev@yandex.ru \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=john.mcnamara@intel.com \
    --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).