From: John Fastabend <john.fastabend@gmail.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v7 1/2] ixgbe: add XDP support for pass and drop actions
Date: Sat, 25 Mar 2017 12:04:04 -0700 [thread overview]
Message-ID: <58D6BF24.3070503@gmail.com> (raw)
In-Reply-To: <1490408627.5679.45.camel@intel.com>
On 17-03-24 07:23 PM, Jeff Kirsher wrote:
> On Thu, 2017-03-23 at 21:31 -0700, John Fastabend wrote:
>> Basic XDP drop support for ixgbe. Uses READ_ONCE/xchg semantics on
>> XDP
>> programs instead of rcu primitives as suggested by Daniel Borkmann
>> and
>> Alex Duyck.
>>
>> Signed-off-by: John Fastabend <john.r.fastabend@intel.com>
>> Acked-by: Alexander Duyck <alexander.h.duyck@intel.com>
>> ---
>> drivers/net/ethernet/intel/ixgbe/ixgbe.h | 4 -
>> drivers/net/ethernet/intel/ixgbe/ixgbe_ethtool.c | 4 -
>> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 163
>> +++++++++++++++++++---
>> 3 files changed, 144 insertions(+), 27 deletions(-)
>
> Does not apply cleanly to my dev-queue branch, what tree did you base
> these changes on?
>
Did you pop off the v6 series? I see its still in your tree :/ Or do you
just want fixes to the initial series?
Thanks,
John
next prev parent reply other threads:[~2017-03-25 19:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 4:30 [Intel-wired-lan] [PATCH v7 0/2] XDP support for ixgbe John Fastabend
2017-03-24 4:31 ` [Intel-wired-lan] [PATCH v7 1/2] ixgbe: add XDP support for pass and drop actions John Fastabend
2017-03-25 2:23 ` Jeff Kirsher
2017-03-25 19:04 ` John Fastabend [this message]
2017-03-26 0:58 ` Jeff Kirsher
2017-03-28 23:10 ` Bowers, AndrewX
2017-04-11 20:31 ` Tantilov, Emil S
2017-03-24 4:31 ` [Intel-wired-lan] [PATCH v7 2/2] ixgbe: add support for XDP_TX action John Fastabend
2017-03-28 23:11 ` Bowers, AndrewX
2017-03-29 1:39 ` Dmitry Popov
2017-03-24 22:22 ` [Intel-wired-lan] [PATCH v7 0/2] XDP support for ixgbe William Tu
2017-03-25 23:55 ` John Fastabend
2017-03-27 18:38 ` William Tu
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=58D6BF24.3070503@gmail.com \
--to=john.fastabend@gmail.com \
--cc=intel-wired-lan@osuosl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox