netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jürgen Groß" <jgross@suse.com>
To: Denis Kirjanov <kda@linux-powerpc.org>
Cc: netdev@vger.kernel.org, ilias.apalodimas@linaro.org,
	wei.liu@kernel.org, paul@xen.org
Subject: Re: [PATCH net-next v4] xen networking: add basic XDP support for xen-netfront
Date: Mon, 23 Mar 2020 11:27:27 +0100	[thread overview]
Message-ID: <9eb74bee-8434-62aa-8158-bae130353670@suse.com> (raw)
In-Reply-To: <CAOJe8K0fBBi-M+Tdv2kC+ZaNvjx92tzYaU1QX2zr8QOBRLwu3g@mail.gmail.com>

On 23.03.20 11:15, Denis Kirjanov wrote:
> On 3/18/20, Jürgen Groß <jgross@suse.com> wrote:
>> On 18.03.20 13:50, Denis Kirjanov wrote:
>>> On 3/18/20, Jürgen Groß <jgross@suse.com> wrote:
>>>> On 16.03.20 14:09, Denis Kirjanov wrote:
>>>>> The patch adds a basic XDP processing to xen-netfront driver.
>>>>>
>>>>> We ran an XDP program for an RX response received from netback
>>>>> driver. Also we request xen-netback to adjust data offset for
>>>>> bpf_xdp_adjust_head() header space for custom headers.
>>>>
>>>> This is in no way a "verbose patch descriprion".
>>>>
>>>> I'm missing:
>>>>
>>>> - Why are you doing this. "Add XDP support" is not enough, for such
>>>>      a change I'd like to see some performance numbers to get an idea
>>>>      of the improvement to expect, or which additional functionality
>>>>      for the user is available.
>>> Ok, I'll try to measure  some numbers.
>>>
>>>>
>>>> - A short description for me as a Xen maintainer with only basic
>>>>      networking know-how, what XDP programs are about (a link to some
>>>>      more detailed doc is enough, of course) and how the interface
>>>>      is working (especially for switching between XDP mode and normal
>>>>      SKB processing).
>>>
>>> You can search for the "A practical introduction to XDP" tutorial.
>>> Actually there is a lot of information available regarding XDP, you
>>> can easily find it.
>>>
>>>>
>>>> - A proper description of the netfront/netback communication when
>>>>      enabling or disabling XDP mode (who is doing what, is silencing
>>>>      of the virtual adapter required, ...).
>>> Currently we need only a header offset from netback driver so that we can
>>> put
>>> custom encapsulation header if required and that's done using xen bus
>>> state switching,
>>> so that:
>>> - netback tells that it can adjust the header offset
>>> - netfront part reads it
>>
>> Yes, but how is this synchronized with currently running network load?
>> Assume you are starting without XDP being active and then you are
>> activating it. How is the synchronization done from which request on
>> the XDP headroom is available?
> 
> Hi Jurgen,
> 
> basically XDP is activated when you've assigned an xdp program to the
> networking device.
> Assigning an xdp program means that we have to adjust a pointer which
> is RCU protected.

This doesn't answer my question.

You have basically two communication channels: the state of the frontend
and backend for activation/deactivation of XDP, and the ring pages with
the rx and tx requests and responses. How is the synchronization between
those two channels done? So how does the other side know which of the
packets in flight will then have XDP on or off?


Juergen

  reply	other threads:[~2020-03-23 10:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16 13:09 [PATCH net-next v4] xen networking: add basic XDP support for xen-netfront Denis Kirjanov
2020-03-16 15:44 ` Jesper Dangaard Brouer
2020-03-18 12:31   ` Denis Kirjanov
2020-03-16 15:52 ` Jesper Dangaard Brouer
2020-03-18 12:30   ` Denis Kirjanov
2020-03-18 10:27 ` Paul Durrant
2020-03-18 11:16 ` Jürgen Groß
2020-03-18 12:50   ` Denis Kirjanov
2020-03-18 13:11     ` Jürgen Groß
2020-03-23 10:15       ` Denis Kirjanov
2020-03-23 10:27         ` Jürgen Groß [this message]
2020-03-23 10:49           ` Denis Kirjanov
2020-03-23 11:00             ` Jürgen Groß
2020-03-30 12:16               ` Denis Kirjanov
2020-03-30 12:55                 ` Jürgen Groß
2020-03-30 13:09                   ` Denis Kirjanov
2020-03-30 13:13                     ` Jürgen Groß
2020-03-30 13:18                       ` Denis Kirjanov

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=9eb74bee-8434-62aa-8158-bae130353670@suse.com \
    --to=jgross@suse.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=kda@linux-powerpc.org \
    --cc=netdev@vger.kernel.org \
    --cc=paul@xen.org \
    --cc=wei.liu@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).