From: "Björn Töpel" <bjorn.topel@gmail.com>
To: Ilias Apalodimas <ilias.apalodimas@linaro.org>
Cc: Netdev <netdev@vger.kernel.org>,
jaswinder.singh@linaro.org, ard.biesheuvel@linaro.org,
masami.hiramatsu@linaro.org, "Arnd Bergmann" <arnd@arndb.de>,
"MykytaI Iziumtsev" <mykyta.iziumtsev@linaro.org>,
"Björn Töpel" <bjorn.topel@intel.com>,
"Karlsson, Magnus" <magnus.karlsson@intel.com>
Subject: Re: [net-next, PATCH 0/2, v1] net: socionext: add AF_XDP support
Date: Mon, 10 Sep 2018 12:06:38 +0200 [thread overview]
Message-ID: <CAJ+HfNh_Z4Z5C1BUSKEOwTYL007LwcEMZ-eoej1qhqe-AZvvbg@mail.gmail.com> (raw)
In-Reply-To: <1536567880-15097-1-git-send-email-ilias.apalodimas@linaro.org>
Den mån 10 sep. 2018 kl 10:26 skrev Ilias Apalodimas
<ilias.apalodimas@linaro.org>:
>
> This patch series adds AF_XDP support socionext netsec driver
>
> - patch [1/2]: Use a different allocation scheme for Rx DMA buffers to prepare
> the driver for AF_XDP support
> - patch [2/2]: Add AF_XDP support without zero-copy
>
> Ilias Apalodimas (2):
> net: socionext: different approach on DMA
> net: socionext: add AF_XDP support
>
You should probably rephrase patch #2. You are adding XDP support, and
AF_XDP just follows from that. Nice to see more XDP support!
Björn
> drivers/net/ethernet/socionext/netsec.c | 444 +++++++++++++++++++++++---------
> 1 file changed, 329 insertions(+), 115 deletions(-)
>
> --
> 2.7.4
>
prev parent reply other threads:[~2018-09-10 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 8:24 [net-next, PATCH 0/2, v1] net: socionext: add AF_XDP support Ilias Apalodimas
2018-09-10 8:24 ` [net-next, PATCH 1/2, v1] net: socionext: different approach on DMA Ilias Apalodimas
2018-09-10 8:24 ` [net-next, PATCH 2/2, v1] net: socionext: add AF_XDP support Ilias Apalodimas
2018-09-10 10:56 ` Toshiaki Makita
2018-09-10 11:20 ` Ilias Apalodimas
2018-09-10 16:21 ` Ilias Apalodimas
2018-09-11 0:45 ` Toshiaki Makita
2018-09-10 10:06 ` Björn Töpel [this message]
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=CAJ+HfNh_Z4Z5C1BUSKEOwTYL007LwcEMZ-eoej1qhqe-AZvvbg@mail.gmail.com \
--to=bjorn.topel@gmail.com \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=bjorn.topel@intel.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jaswinder.singh@linaro.org \
--cc=magnus.karlsson@intel.com \
--cc=masami.hiramatsu@linaro.org \
--cc=mykyta.iziumtsev@linaro.org \
--cc=netdev@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).