From: Michael Chan <michael.chan@broadcom.com>
To: David Miller <davem@davemloft.net>
Cc: Netdev <netdev@vger.kernel.org>, xdp-newbies@vger.kernel.org
Subject: Re: [PATCH v4 net-next RFC] net: Generic XDP
Date: Thu, 13 Apr 2017 13:16:43 -0700 [thread overview]
Message-ID: <CACKFLikm1vDzz8eQJMJOEsbv-NNV41ki2TEPVPCSpP6VjaowBA@mail.gmail.com> (raw)
In-Reply-To: <20170413.120925.2082322246776478766.davem@davemloft.net>
On Thu, Apr 13, 2017 at 9:09 AM, David Miller <davem@davemloft.net> wrote:
>
> ---
>
> v4:
> - Fix MAC header adjustmnet before calling prog (David Ahern)
> - Disable LRO when generic XDP is installed (Michael Chan)
I don't see where you are disabling LRO in the patch.
> - Bypass qdisc et al. on XDP_TX and record the event (Alexei)
> - Do not perform generic XDP on reinjected packets (DaveM)
>
next prev parent reply other threads:[~2017-04-13 20:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 16:09 [PATCH v4 net-next RFC] net: Generic XDP David Miller
2017-04-13 20:16 ` Michael Chan [this message]
2017-04-13 20:23 ` David Miller
2017-04-14 1:59 ` [lkp-robot] [net] d1dff7db3b: net/core/dev.c:#suspicious_rcu_dereference_check()usage kernel test robot
2017-04-15 0:59 ` [PATCH v4 net-next RFC] net: Generic XDP Alexei Starovoitov
2017-04-15 15:46 ` David Ahern
2017-04-18 19:05 ` Andy Gospodarek
2017-04-18 19:07 ` David Miller
2017-04-18 19:29 ` David Miller
2017-04-18 19:37 ` Andy Gospodarek
2017-04-19 14:29 ` Andy Gospodarek
2017-04-19 17:17 ` Alexei Starovoitov
2017-04-19 17:44 ` John Fastabend
2017-04-19 20:25 ` Andy Gospodarek
2017-04-20 0:13 ` Alexei Starovoitov
2017-04-20 1:40 ` David Miller
2017-04-20 22:09 ` Andy Gospodarek
2017-04-20 14:30 ` Jesper Dangaard Brouer
2017-04-24 13:18 ` Jesper Dangaard Brouer
2017-04-18 20:26 ` Jesper Dangaard Brouer
2017-04-14 16:33 ` William Tu
2017-04-24 14:24 ` Blogpost evaluation this " Jesper Dangaard Brouer
2017-04-24 22:26 ` David Miller
2017-04-25 8:28 ` Jesper Dangaard Brouer
2017-04-25 17:25 ` Andy Gospodarek
2017-04-25 17:31 ` David Miller
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=CACKFLikm1vDzz8eQJMJOEsbv-NNV41ki2TEPVPCSpP6VjaowBA@mail.gmail.com \
--to=michael.chan@broadcom.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=xdp-newbies@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).