From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
John Fastabend <john.fastabend@gmail.com>,
bblanco@plumgrid.com, jeffrey.t.kirsher@intel.com,
davem@davemloft.net, xiyou.wangcong@gmail.com,
intel-wired-lan@lists.osuosl.org, u9012063@gmail.com,
netdev@vger.kernel.org, brouer@redhat.com
Subject: Re: [net-next PATCH v3 2/3] e1000: add initial XDP support
Date: Sun, 18 Sep 2016 19:25:14 +0200 [thread overview]
Message-ID: <20160918192514.510d4702@redhat.com> (raw)
In-Reply-To: <1473723968.18970.111.camel@edumazet-glaptop3.roam.corp.google.com>
On Mon, 12 Sep 2016 16:46:08 -0700
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> This XDP_TX thing was one of the XDP marketing stuff, but there is
> absolutely no documentation on it, warning users about possible
> limitations/outcomes.
I will take care of documentation for the XDP project.
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
Author of http://www.iptv-analyzer.org
LinkedIn: http://www.linkedin.com/in/brouer
WARNING: multiple messages have this Message-ID (diff)
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [net-next PATCH v3 2/3] e1000: add initial XDP support
Date: Sun, 18 Sep 2016 19:25:14 +0200 [thread overview]
Message-ID: <20160918192514.510d4702@redhat.com> (raw)
In-Reply-To: <1473723968.18970.111.camel@edumazet-glaptop3.roam.corp.google.com>
On Mon, 12 Sep 2016 16:46:08 -0700
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> This XDP_TX thing was one of the XDP marketing stuff, but there is
> absolutely no documentation on it, warning users about possible
> limitations/outcomes.
I will take care of documentation for the XDP project.
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
Author of http://www.iptv-analyzer.org
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2016-09-18 17:25 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 22:13 [net-next PATCH v3 0/3] e1000 XDP implementation John Fastabend
2016-09-12 22:13 ` [Intel-wired-lan] " John Fastabend
2016-09-12 22:13 ` [net-next PATCH v3 1/3] e1000: track BQL bytes regardless of skb or not John Fastabend
2016-09-12 22:13 ` [Intel-wired-lan] " John Fastabend
2016-09-13 3:00 ` Alexander Duyck
2016-09-13 3:00 ` Alexander Duyck
2016-09-13 4:25 ` Tom Herbert
2016-09-13 4:25 ` Tom Herbert
2016-09-13 13:17 ` Alexander Duyck
2016-09-13 13:17 ` Alexander Duyck
2016-09-14 23:57 ` Brown, Aaron F
2016-09-14 23:57 ` Brown, Aaron F
2016-09-15 0:43 ` Alexei Starovoitov
2016-09-15 0:43 ` Alexei Starovoitov
2016-09-15 4:22 ` John Fastabend
2016-09-15 4:22 ` John Fastabend
2016-09-15 23:29 ` Brown, Aaron F
2016-09-15 23:29 ` Brown, Aaron F
2016-09-12 22:13 ` [net-next PATCH v3 2/3] e1000: add initial XDP support John Fastabend
2016-09-12 22:13 ` [Intel-wired-lan] " John Fastabend
2016-09-12 22:46 ` Eric Dumazet
2016-09-12 22:46 ` [Intel-wired-lan] " Eric Dumazet
2016-09-12 23:07 ` Alexei Starovoitov
2016-09-12 23:07 ` [Intel-wired-lan] " Alexei Starovoitov
2016-09-12 23:46 ` Eric Dumazet
2016-09-12 23:46 ` [Intel-wired-lan] " Eric Dumazet
2016-09-13 0:03 ` Tom Herbert
2016-09-13 0:03 ` [Intel-wired-lan] " Tom Herbert
2016-09-13 1:28 ` Alexei Starovoitov
2016-09-13 1:28 ` [Intel-wired-lan] " Alexei Starovoitov
2016-09-13 16:21 ` Tom Herbert
2016-09-13 16:21 ` [Intel-wired-lan] " Tom Herbert
2016-09-13 17:13 ` Alexei Starovoitov
2016-09-13 17:13 ` [Intel-wired-lan] " Alexei Starovoitov
2016-09-13 17:37 ` Eric Dumazet
2016-09-13 17:37 ` [Intel-wired-lan] " Eric Dumazet
2016-09-13 17:59 ` Alexei Starovoitov
2016-09-13 17:59 ` [Intel-wired-lan] " Alexei Starovoitov
2016-09-13 18:28 ` Rustad, Mark D
2016-09-13 18:28 ` Rustad, Mark D
2016-09-13 18:30 ` Alexei Starovoitov
2016-09-13 18:30 ` Alexei Starovoitov
2016-09-13 19:14 ` Rustad, Mark D
2016-09-13 19:14 ` Rustad, Mark D
2016-09-13 21:52 ` Alexei Starovoitov
2016-09-13 21:52 ` Alexei Starovoitov
2016-09-13 22:41 ` Rustad, Mark D
2016-09-13 22:41 ` Rustad, Mark D
2016-09-13 23:40 ` Alexei Starovoitov
2016-09-13 23:40 ` Alexei Starovoitov
2016-09-14 0:13 ` Rustad, Mark D
2016-09-14 0:13 ` Rustad, Mark D
2016-09-14 23:42 ` Brown, Aaron F
2016-09-14 23:42 ` Brown, Aaron F
2016-09-13 23:17 ` Francois Romieu
2016-09-13 23:17 ` Francois Romieu
2016-09-13 17:55 ` Tom Herbert
2016-09-13 17:55 ` [Intel-wired-lan] " Tom Herbert
2016-09-13 1:21 ` Alexei Starovoitov
2016-09-13 1:21 ` [Intel-wired-lan] " Alexei Starovoitov
2016-09-18 17:25 ` Jesper Dangaard Brouer [this message]
2016-09-18 17:25 ` Jesper Dangaard Brouer
2016-09-18 18:06 ` Tom Herbert
2016-09-13 3:42 ` Alexander Duyck
2016-09-13 3:42 ` Alexander Duyck
2016-09-13 16:56 ` Alexei Starovoitov
2016-09-13 16:56 ` Alexei Starovoitov
2016-09-12 22:14 ` [net-next PATCH v3 3/3] e1000: bundle xdp xmit routines John Fastabend
2016-09-12 22:14 ` [Intel-wired-lan] " John Fastabend
2016-09-12 23:45 ` Tom Herbert
2016-09-12 23:45 ` [Intel-wired-lan] " Tom Herbert
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=20160918192514.510d4702@redhat.com \
--to=brouer@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bblanco@plumgrid.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=u9012063@gmail.com \
--cc=xiyou.wangcong@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.