From: Paul Durrant <xadimgnik@gmail.com>
To: "'Denis Kirjanov'" <kda@linux-powerpc.org>
Cc: <netdev@vger.kernel.org>, <jgross@suse.com>, <wei.liu@kernel.org>,
<ilias.apalodimas@linaro.org>
Subject: RE: [PATCH net-next v7 2/2] xen networking: add XDP offset adjustment to xen-netback
Date: Tue, 5 May 2020 17:28:00 +0100 [thread overview]
Message-ID: <005a01d622fa$25745e40$705d1ac0$@xen.org> (raw)
In-Reply-To: <CAOJe8K3sByKRgecjYBnm35_Kijaqu0TTruQwvddEu1tkF-TEVg@mail.gmail.com>
> -----Original Message-----
> >> @@ -417,6 +431,11 @@ static void frontend_changed(struct xenbus_device
> >> *dev,
> >> set_backend_state(be, XenbusStateConnected);
> >> break;
> >>
> >> + case XenbusStateReconfiguring:
> >> + read_xenbus_frontend_xdp(be, dev);
> >
> > Is the frontend always expected to trigger a re-configure, or could
> > feature-xdp already be enabled prior to connection?
>
> Yes, feature-xdp is set by the frontend when xdp code is loaded.
>
That's still ambiguous... what I'm getting at is whether you also need to read the xdp state when transitioning into Connected as well as Reconfiguring?
Paul
next prev parent reply other threads:[~2020-05-05 16:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 8:37 [PATCH net-next v7 1/2] xen networking: add basic XDP support for xen-netfront Denis Kirjanov
2020-05-04 8:37 ` [PATCH net-next v7 2/2] xen networking: add XDP offset adjustment to xen-netback Denis Kirjanov
2020-05-05 14:19 ` Paul Durrant
2020-05-05 15:57 ` Denis Kirjanov
2020-05-05 16:28 ` Paul Durrant [this message]
2020-05-06 17:45 ` Denis Kirjanov
2020-05-07 7:18 ` Paul Durrant
2020-05-07 11:30 ` Denis Kirjanov
2020-05-05 8:33 ` [PATCH net-next v7 1/2] xen networking: add basic XDP support for xen-netfront Jesper Dangaard Brouer
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='005a01d622fa$25745e40$705d1ac0$@xen.org' \
--to=xadimgnik@gmail.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jgross@suse.com \
--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).