From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [net-next RFC 0/8] multiqueue API support for macvtap
Date: Thu, 23 May 2013 14:53:27 +0300 [thread overview]
Message-ID: <20130523115327.GE17993@redhat.com> (raw)
In-Reply-To: <1369278753-2533-1-git-send-email-jasowang@redhat.com>
On Thu, May 23, 2013 at 11:12:25AM +0800, Jason Wang wrote:
> Hi all:
>
> This series implements a fully tuntap compatiable API which could be used by
> userspace to manage multi macvtap queues. The main parts is to add TUNSETQUEUE
> ioctl support for macvtap.
>
> Patch 1 - 4 was some tuntap compatibility and misc cleanups.
> Patch 5 removes the linear search in macvtap by reshuffling the macvtaps array
> each time a queue is removed. After this, we could store both enabled and
> disabled queues in the same array without introducing extra data structure.
> Patch 6 let TUNSETIFF can create multiqueue device, nothing but some check were
> added.
> Patch 7 implement TUNSETQUEUE ioctl
> Patch 8 reports IFF_MULTI_QUEUE to userspace to notify the userspace that the
> multiqueue API is completed.
>
> Flow caches implememtation were missed in this version, since I am doing rework
> on the tuntap flow caches. Have some some stress test with both netperf and
> pktgen.
>
> Please review, thanks.
Overall looks good. Sent some comments on specific patches.
Thanks!
> Jason Wang (8):
> macvlan: switch to use IS_ENABLED()
> macvtap: return -EBADFD when TUNGETIFF fails
> macvtap: introduce macvtap_get_vlan()
> macvlan: reduce the max number of taps to 8
> macvtap: eliminate linear search
> macvtap: allow TUNSETIFF to create multiqueue device
> macvtap: add TUNSETQUEUE ioctl
> macvtap: enable multiqueue flag
>
> drivers/net/macvtap.c | 265 ++++++++++++++++++++++++++++++-------------
> include/linux/if_macvlan.h | 11 ++-
> 2 files changed, 194 insertions(+), 82 deletions(-)
prev parent reply other threads:[~2013-05-23 11:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 3:12 [net-next RFC 0/8] multiqueue API support for macvtap Jason Wang
2013-05-23 3:12 ` [net-next RFC 1/8] macvlan: switch to use IS_ENABLED() Jason Wang
2013-05-23 11:31 ` Michael S. Tsirkin
2013-05-23 3:12 ` [net-next RFC 2/8] macvtap: return -EBADFD when TUNGETIFF fails Jason Wang
2013-05-23 11:54 ` Michael S. Tsirkin
2013-05-24 6:28 ` Jason Wang
2013-05-23 3:12 ` [net-next RFC 3/8] macvtap: introduce macvtap_get_vlan() Jason Wang
2013-05-23 15:11 ` Sergei Shtylyov
2013-05-24 6:21 ` Jason Wang
2013-05-23 3:12 ` [net-next RFC 4/8] macvlan: reduce the max number of taps to 8 Jason Wang
2013-05-23 6:37 ` Michael S. Tsirkin
2013-05-24 5:14 ` Jason Wang
2013-05-23 3:12 ` [net-next RFC 5/8] macvtap: eliminate linear search Jason Wang
2013-05-23 11:41 ` Michael S. Tsirkin
2013-05-24 5:33 ` Jason Wang
2013-05-23 3:12 ` [net-next RFC 6/8] macvtap: allow TUNSETIFF to create multiqueue device Jason Wang
2013-05-23 11:45 ` Michael S. Tsirkin
2013-05-24 5:36 ` Jason Wang
2013-05-23 3:12 ` [net-next RFC 7/8] macvtap: add TUNSETQUEUE ioctl Jason Wang
2013-05-23 11:52 ` Michael S. Tsirkin
2013-05-24 6:19 ` Jason Wang
2013-05-23 3:12 ` [net-next RFC 8/8] macvtap: enable multiqueue flag Jason Wang
2013-05-23 11:53 ` Michael S. Tsirkin [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=20130523115327.GE17993@redhat.com \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.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).