From: Stephen Hemminger <stephen@networkplumber.org>
To: "Samudrala, Sridhar" <sridhar.samudrala@intel.com>
Cc: Jiri Pirko <jiri@resnulli.us>,
mst@redhat.com, davem@davemloft.net, netdev@vger.kernel.org,
virtio-dev@lists.oasis-open.org, jesse.brandeburg@intel.com,
alexander.h.duyck@intel.com, kubakici@wp.pl
Subject: Re: [PATCH v4 2/2] virtio_net: Extend virtio to use VF datapath when available
Date: Tue, 13 Mar 2018 17:54:06 -0700 [thread overview]
Message-ID: <20180313175406.32fddf33@xeon-e3> (raw)
In-Reply-To: <45ca2aec-6475-06e6-7a38-be6b8aeb362b@intel.com>
On Tue, 13 Mar 2018 17:36:23 -0700
"Samudrala, Sridhar" <sridhar.samudrala@intel.com> wrote:
> OK. looks like you want to see atleast some code shared between netvsc and virtio_net
> even when they are using 2 different netdev models.
> Will try to add a new file under net/core and move some functions that can be shared
> between netvsc and virtio_net in BACKUP mode.
Make it work first (on both) then workout how to share.
That method worked quite well for tunnels and other netdev like objects.
next prev parent reply other threads:[~2018-03-14 0:54 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 20:08 [PATCH v4 0/2] Enable virtio_net to act as a backup for a passthru device Sridhar Samudrala
2018-03-01 20:08 ` [PATCH v4 1/2] virtio_net: Introduce VIRTIO_NET_F_BACKUP feature bit Sridhar Samudrala
2018-03-01 20:08 ` [PATCH v4 2/2] virtio_net: Extend virtio to use VF datapath when available Sridhar Samudrala
2018-03-02 8:36 ` Jiri Pirko
2018-03-02 15:26 ` Alexander Duyck
2018-03-02 16:20 ` Jiri Pirko
2018-03-02 16:37 ` Samudrala, Sridhar
2018-03-02 17:06 ` Alexander Duyck
2018-03-02 19:42 ` Michael S. Tsirkin
2018-03-02 20:49 ` Siwei Liu
2018-03-03 11:31 ` Jiri Pirko
2018-03-03 18:04 ` Alexander Duyck
2018-03-03 21:25 ` Jiri Pirko
2018-03-04 0:26 ` Alexander Duyck
2018-03-04 7:13 ` Jiri Pirko
2018-03-04 18:24 ` Alexander Duyck
2018-03-04 18:50 ` Jiri Pirko
2018-03-04 21:54 ` Samudrala, Sridhar
2018-03-04 21:58 ` Alexander Duyck
2018-03-05 9:21 ` Jiri Pirko
2018-03-05 16:11 ` Stephen Hemminger
2018-03-05 22:30 ` Jiri Pirko
2018-03-05 22:47 ` Alexander Duyck
2018-03-06 3:15 ` Stephen Hemminger
2018-03-06 19:08 ` Alexander Duyck
2018-03-06 22:59 ` Jiri Pirko
2018-03-06 23:27 ` Alexander Duyck
2018-03-07 2:38 ` Michael S. Tsirkin
2018-03-07 17:50 ` Alexander Duyck
2018-03-07 18:06 ` Stephen Hemminger
2018-03-07 18:55 ` Alexander Duyck
2018-03-07 20:11 ` Michael S. Tsirkin
2018-03-12 18:47 ` Samudrala, Sridhar
2018-03-02 19:41 ` Michael S. Tsirkin
2018-03-02 19:52 ` Samudrala, Sridhar
2018-03-02 20:10 ` Michael S. Tsirkin
2018-03-02 20:44 ` Siwei Liu
2018-03-02 20:56 ` Samudrala, Sridhar
2018-03-02 21:33 ` Michael S. Tsirkin
2018-03-02 21:31 ` Michael S. Tsirkin
2018-03-02 22:26 ` Siwei Liu
2018-03-04 4:00 ` Michael S. Tsirkin
2018-03-02 21:11 ` Siwei Liu
2018-03-02 21:36 ` Michael S. Tsirkin
2018-03-02 23:56 ` Siwei Liu
2018-03-04 4:04 ` Michael S. Tsirkin
2018-03-12 21:53 ` Siwei Liu
2018-03-02 23:12 ` Samudrala, Sridhar
2018-03-03 0:09 ` Siwei Liu
2018-03-12 20:12 ` Jiri Pirko
2018-03-12 20:58 ` Samudrala, Sridhar
2018-03-12 21:08 ` Jiri Pirko
2018-03-14 0:36 ` Samudrala, Sridhar
2018-03-14 0:54 ` Stephen Hemminger [this message]
2018-03-14 15:45 ` Jiri Pirko
2018-03-12 22:44 ` Siwei Liu
2018-03-14 0:28 ` Samudrala, Sridhar
2018-03-14 0:44 ` Michael S. Tsirkin
2018-03-14 4:50 ` Siwei Liu
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=20180313175406.32fddf33@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=alexander.h.duyck@intel.com \
--cc=davem@davemloft.net \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=kubakici@wp.pl \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sridhar.samudrala@intel.com \
--cc=virtio-dev@lists.oasis-open.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).