DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Sujith Sankar (ssujith)" <ssujith@cisco.com>
Cc: dev@dpdk.org, "Prasad Rao \(prrao\)" <prrao@cisco.com>
Subject: Re: [dpdk-dev] [PATCH v6 0/6] enicpmd: Cisco Systems Inc. VIC Ethernet PMD
Date: Fri, 27 Feb 2015 11:46:46 +0100	[thread overview]
Message-ID: <1457719.Qg0ZkTa88V@xps13> (raw)
In-Reply-To: <D1162370.313E9%ssujith@cisco.com>

2015-02-27 08:09, Sujith Sankar:
> Hi Thomas,
> 
> No update on it from my side :-(
> It would take some more time for me to start working on it (and flow
> director api) as a few other things are keeping me busy.

It's unfortunate.
We now have a PMD without documentation and blocking the removal of the
old flow director API.
Is there someone else at Cisco able to work on it?
I think the first priority should be on the flow director API as it has a
wider impact.

Thanks

  parent reply	other threads:[~2015-02-27 10:47 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25 17:26 Sujith Sankar
2014-11-25 17:26 ` [dpdk-dev] [PATCH v6 1/6] enicpmd: License text Sujith Sankar
2014-11-25 17:26 ` [dpdk-dev] [PATCH v6 2/6] enicpmd: Makefile Sujith Sankar
2014-11-25 17:26 ` [dpdk-dev] [PATCH v6 3/6] enicpmd: VNIC common code partially shared with ENIC kernel mode driver Sujith Sankar
2014-11-25 17:26 ` [dpdk-dev] [PATCH v6 4/6] enicpmd: pmd specific code Sujith Sankar
2014-11-27 14:49   ` Wodkowski, PawelX
2014-11-25 17:26 ` [dpdk-dev] [PATCH v6 5/6] enicpmd: DPDK-ENIC PMD interface Sujith Sankar
2014-12-29  8:15   ` Wu, Jingjing
2014-12-30  4:45     ` Sujith Sankar (ssujith)
2015-01-06  9:41       ` Thomas Monjalon
2015-01-30  8:53       ` Wu, Jingjing
2014-11-25 17:26 ` [dpdk-dev] [PATCH v6 6/6] enicpmd: DPDK changes for accommodating ENIC PMD Sujith Sankar
2014-11-25 19:51 ` [dpdk-dev] [PATCH v6 0/6] enicpmd: Cisco Systems Inc. VIC Ethernet PMD David Marchand
2014-11-26 22:11   ` Thomas Monjalon
2014-11-27  4:27     ` Sujith Sankar (ssujith)
2014-11-27 15:31       ` Thomas Monjalon
2015-01-20 11:25         ` David Marchand
2015-01-21  5:03           ` Sujith Sankar (ssujith)
2015-02-26 11:49             ` Thomas Monjalon
2015-02-26 13:08               ` Wiles, Keith
2015-02-27  8:09                 ` Sujith Sankar (ssujith)
2015-02-27  8:47                   ` [dpdk-dev] Why only rx queue "0" can receive network packet by i40e NIC lhffjzh
2015-02-27  9:03                     ` lhffjzh
2015-02-27 10:55                     ` Thomas Monjalon
2015-02-28  1:47                       ` lhffjzh
2015-02-28  3:17                         ` Zhang, Helin
2015-02-28  4:33                           ` lhffjzh
2015-02-28 14:33                             ` Zhang, Helin
2015-07-23  0:47                               ` Jeff Venable, Sr.
2015-07-23  0:56                                 ` Zhang, Helin
2015-07-30  1:58                                   ` Jeff Venable, Sr.
2015-07-31 15:35                                     ` Zhang, Helin
2015-02-27 10:46                   ` Thomas Monjalon [this message]
2015-03-11  9:05                     ` [dpdk-dev] [PATCH v6 0/6] enicpmd: Cisco Systems Inc. VIC Ethernet PMD Sujith Sankar (ssujith)
2015-05-11  9:25                   ` Thomas Monjalon
2014-11-25 20:11 ` Neil Horman

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=1457719.Qg0ZkTa88V@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=prrao@cisco.com \
    --cc=ssujith@cisco.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).