From: Venky Venkatesan <venky.venkatesan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [RFC PATCH] ethdev: remove old flow director API
Date: Mon, 20 Apr 2015 09:45:59 -0700 [thread overview]
Message-ID: <55352D47.8010906@intel.com> (raw)
In-Reply-To: <20150420163348.GA19573-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
On 04/20/2015 09:33 AM, Neil Horman wrote:
> On Mon, Apr 20, 2015 at 04:11:43PM +0200, Thomas Monjalon wrote:
>> It's time to remove this old API.
>> It seems some work is still needed to rely only on eth_ctrl API.
>> At least ixgbe, i40e and testpmd must be fixed.
>> Jingjing, do you think it's possible to remove all these structures
>> from rte_ethdev.h?
>>
>> Thanks
>>
> NAK.
>
> I'm certainly not opposed to removing the API's if they are truly no longer
> needed. But they have been codified as part of the ABI, so the deprecation
> schedule needs to be followed. Given what you've said above, it seems like that
> might be worthwhile anyway, as it will provide the needed runway to allow users
> to convert to the new API.
>
> Neil
+1 NAK. Agree with Neil.
next prev parent reply other threads:[~2015-04-20 16:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 14:11 [RFC PATCH] ethdev: remove old flow director API Thomas Monjalon
[not found] ` <1429539103-15885-1-git-send-email-thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2015-04-20 14:32 ` Wu, Jingjing
[not found] ` <9BB6961774997848B5B42BEC655768F8BFFDF1-0J0gbvR4kTg/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-04-20 14:59 ` Thomas Monjalon
2015-04-22 8:26 ` Wu, Jingjing
2015-04-20 16:33 ` Neil Horman
[not found] ` <20150420163348.GA19573-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2015-04-20 16:45 ` Venky Venkatesan [this message]
[not found] ` <55352D47.8010906-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-04-27 16:08 ` Thomas Monjalon
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=55352D47.8010906@intel.com \
--to=venky.venkatesan-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.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 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.