From: Wenzhuo Lu <wenzhuo.lu@intel.com>
To: ferruh.yigit@intel.com
Cc: dev@dpdk.org, Wenzhuo Lu <wenzhuo.lu@intel.com>
Subject: [dpdk-dev] [PATCH 0/3] AVF optimization
Date: Thu, 11 Jan 2018 14:52:34 +0800 [thread overview]
Message-ID: <1515653557-63430-1-git-send-email-wenzhuo.lu@intel.com> (raw)
The optimization for AVF code.
As the AVF patches is in the next-net repo but not merged
to the master branch, proposed these patches that can be
merged to the previouse ones.
Sorry for the inconvenience.
Wenzhuo Lu (3):
net/avf/base: add spinlock functions
net/avf: remove spinlock functions
net/avf: remove useless code
drivers/net/avf/avf.h | 3 ---
drivers/net/avf/avf_ethdev.c | 24 ------------------------
drivers/net/avf/base/avf_osdep.h | 23 +++++++++++++++++++++++
3 files changed, 23 insertions(+), 27 deletions(-)
--
1.9.3
next reply other threads:[~2018-01-11 6:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 6:52 Wenzhuo Lu [this message]
2018-01-11 6:52 ` [dpdk-dev] [PATCH 1/3] net/avf/base: add spinlock functions Wenzhuo Lu
2018-01-11 6:52 ` [dpdk-dev] [PATCH 2/3] net/avf: remove " Wenzhuo Lu
2018-01-11 6:52 ` [dpdk-dev] [PATCH 3/3] net/avf: remove useless code Wenzhuo Lu
2018-01-11 14:24 ` [dpdk-dev] [PATCH 0/3] AVF optimization Ferruh Yigit
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=1515653557-63430-1-git-send-email-wenzhuo.lu@intel.com \
--to=wenzhuo.lu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).