DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Qiu, Michael" <michael.qiu@intel.com>
To: "Wu, Jingjing" <jingjing.wu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/4] Integrate ethertype filter in igb/ixgbe	driver to new API
Date: Thu, 25 Dec 2014 03:27:09 +0000	[thread overview]
Message-ID: <533710CFB86FA344BFBF2D6802E60286CA27E3@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1419477270-14611-1-git-send-email-jingjing.wu@intel.com>

Hi Jingjing,

Would you mind to tell me why need new APIs? Any functional or
performance increase?
Better to state in commit log.

You know it should be careful to change APIs, especially for user
interface. 

Thanks,
Michael
On 12/25/2014 11:14 AM, Jingjing Wu wrote:
> The patch set uses new filter_ctrl API to replace old ethertype filter APIs.
> It uses new functions and structure to replace old ones in igb/ixgbe driver,
> new commands to replace old ones in testpmd, and removes the old APIs. 
>
> Jingjing Wu (4):
>   ixgbe: new functions replaces old ones for ethertype filters
>   e1000: new functions replaces old ones for ethertype filters
>   testpmd: new commands for ethertype filter
>   ethdev: remove old APIs and structures of ethertype filters
>
>  app/test-pmd/cmdline.c              | 253 ++++++++++++--------------
>  app/test-pmd/config.c               |  27 ---
>  lib/librte_ether/rte_ethdev.c       |  57 ------
>  lib/librte_ether/rte_ethdev.h       |  88 ---------
>  lib/librte_pmd_e1000/e1000_ethdev.h |  13 ++
>  lib/librte_pmd_e1000/igb_ethdev.c   | 332 +++++++++++++++++++++------------
>  lib/librte_pmd_ixgbe/ixgbe_ethdev.c | 354 +++++++++++++++++++++++-------------
>  lib/librte_pmd_ixgbe/ixgbe_ethdev.h |  13 ++
>  8 files changed, 579 insertions(+), 558 deletions(-)
>


  parent reply	other threads:[~2014-12-25  3:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-25  3:14 Jingjing Wu
2014-12-25  3:14 ` [dpdk-dev] [PATCH 1/4] ixgbe: new functions replace old ones for ethertype filter Jingjing Wu
2014-12-25  3:14 ` [dpdk-dev] [PATCH 2/4] e1000: new functions replace old ones for ethertype filters Jingjing Wu
2015-01-12  1:32   ` Zhang, Helin
2014-12-25  3:14 ` [dpdk-dev] [PATCH 3/4] testpmd: new commands for ethertype filter Jingjing Wu
2014-12-25  3:14 ` [dpdk-dev] [PATCH 4/4] ethdev: remove old APIs and structures of " Jingjing Wu
2014-12-25  3:27 ` Qiu, Michael [this message]
2014-12-25  3:39   ` [dpdk-dev] [PATCH 0/4] Integrate ethertype filter in igb/ixgbe driver to new API Wu, Jingjing
2014-12-25  4:57     ` Qiu, Michael
2015-01-12  7:16 ` [dpdk-dev] [PATCH v2 " Jingjing Wu
2015-01-12  7:16   ` [dpdk-dev] [PATCH v2 1/4] ixgbe: new functions replace old ones for ethertype filter Jingjing Wu
2015-01-12  7:16   ` [dpdk-dev] [PATCH v2 2/4] e1000: " Jingjing Wu
2015-01-12  7:16   ` [dpdk-dev] [PATCH v2 3/4] testpmd: new commands " Jingjing Wu
2015-01-20 10:14     ` Thomas Monjalon
2015-01-12  7:16   ` [dpdk-dev] [PATCH v2 4/4] ethdev: remove old APIs and structures of " Jingjing Wu
2015-01-12  7:23   ` [dpdk-dev] [PATCH v2 0/4] Integrate ethertype filter in igb/ixgbe driver to new API Zhang, Helin
2015-01-20  8:17     ` 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=533710CFB86FA344BFBF2D6802E60286CA27E3@SHSMSX101.ccr.corp.intel.com \
    --to=michael.qiu@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.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).