netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Edward Cree <ecree@solarflare.com>
Cc: David Miller <davem@davemloft.net>, <netdev@vger.kernel.org>,
	<linux-net-drivers@solarflare.com>, <mhabets@solarflare.com>,
	<cmclachlan@solarflare.com>, <ilias.apalodimas@linaro.org>,
	<lorenzo@kernel.org>, <sameehj@amazon.com>,
	brouer@redhat.com
Subject: Re: [PATCH net-next] sfc: fix XDP-redirect in this driver
Date: Mon, 16 Mar 2020 11:35:15 +0100	[thread overview]
Message-ID: <20200316113515.16f7e243@carbon> (raw)
In-Reply-To: <98fd3c0c-225b-d64c-a64f-ca497205d4ce@solarflare.com>

On Mon, 16 Mar 2020 10:10:01 +0000
Edward Cree <ecree@solarflare.com> wrote:

> On 16/03/2020 08:49, David Miller wrote:
> > Solarflare folks, please review.  
>
> This looks like a correct implementation of what it purports to do, so
> Acked-by: Edward Cree <ecree@solarflare.com>

Thanks for the review!

> It did take me some digging to understand _why_ it was needed though;
>  Jesper, is there any documentation of the tailroom requirement?  It
>  doesn't seem to be mentioned anywhere I could find.

I admit that is is poorly documented.  It is a requirement as both
cpumap and veth have a dependency when they process the redirected
packet.  We/I also need to update the doc on one page per packet
requirement, as it is (in-practice) no longer true.

I'm noticing these bugs, because I'm working on a patchset that add
tailroom extend, and also reserves this 'skb_shared_info' tailroom area.
The real goal is to later add XDP multi-buffer support, using this
'skb_shared_info' tailroom area, as desc here[2]

[2] https://github.com/xdp-project/xdp-project/blob/master/areas/core/xdp-multi-buffer01-design.org

> (Is there even any up-to-date doc of the XDP driver interface?  The
>  one at [1] looks a bit stale...)
> -Ed
> 
> [1]: https://prototype-kernel.readthedocs.io/en/latest/networking/XDP/design/requirements.html

This is my old and out-dated documentation. I didn't know people were
still referring to this.  I does score quite high on Google, so I
guess, that I really need to update this documentation.  (It was my
plan that this would be merged into kernel tree, but I can see it have
been bit-rotting for too long).

-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Principal Kernel Engineer at Red Hat
  LinkedIn: http://www.linkedin.com/in/brouer


  reply	other threads:[~2020-03-16 10:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-13 13:25 [PATCH net-next] sfc: fix XDP-redirect in this driver Jesper Dangaard Brouer
2020-03-16  8:49 ` David Miller
2020-03-16 10:10   ` Edward Cree
2020-03-16 10:35     ` Jesper Dangaard Brouer [this message]
2020-03-16 10:45       ` Denis Kirjanov
2020-03-16 11:55         ` Jesper Dangaard Brouer
2020-03-17  1:22 ` 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=20200316113515.16f7e243@carbon \
    --to=brouer@redhat.com \
    --cc=cmclachlan@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=ecree@solarflare.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=linux-net-drivers@solarflare.com \
    --cc=lorenzo@kernel.org \
    --cc=mhabets@solarflare.com \
    --cc=netdev@vger.kernel.org \
    --cc=sameehj@amazon.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).