From: Jason Wang <jasowang@redhat.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, mst@redhat.com, maxk@qualcomm.com,
haixiao@juniper.net, ernesto.martin@viasat.com,
krkumar2@in.ibm.com, edumazet@google.com
Subject: Re: [net-next v4 0/7] Multiqueue support in tuntap
Date: Thu, 01 Nov 2012 13:07:40 +0800 [thread overview]
Message-ID: <5092039C.60009@redhat.com> (raw)
In-Reply-To: <20121030165249.4cc4d596@nehalam.linuxnetplumber.net>
On 10/31/2012 07:52 AM, Stephen Hemminger wrote:
> I am testing BQL for tuntap.
> It wouldn't be hard to do BQL in the multi-queue version.
Yes, if BQL for tuntap is in first, I will rebase and convert it to
multiqueue version.
Thanks
prev parent reply other threads:[~2012-11-01 5:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 5:35 [net-next v4 0/7] Multiqueue support in tuntap Jason Wang
2012-10-29 5:35 ` [PATCH] tuntap: choose the txq based on rxq Jason Wang
2012-10-29 6:03 ` Jason Wang
2012-10-29 5:35 ` [net-next v4 1/7] tuntap: log the unsigned informaiton with %u Jason Wang
2012-10-29 5:35 ` [net-next v4 2/7] tuntap: move socket to tun_file Jason Wang
2012-10-29 5:36 ` [net-next v4 3/7] tuntap: RCUify dereferencing between tun_struct and tun_file Jason Wang
2012-10-29 5:36 ` [net-next v4 4/7] tuntap: introduce multiqueue flags Jason Wang
2012-10-29 5:36 ` [net-next v4 5/7] tuntap: multiqueue support Jason Wang
2012-10-29 5:36 ` [net-next v4 6/7] tuntap: add ioctl to attach or detach a file form tuntap device Jason Wang
2012-10-29 5:36 ` [net-next v4 7/7] tuntap: choose the txq based on rxq Jason Wang
2012-10-29 6:07 ` [net-next v4 0/7] Multiqueue support in tuntap David Miller
2012-10-29 6:16 ` Jason Wang
2012-10-30 23:52 ` Stephen Hemminger
2012-11-01 5:07 ` Jason Wang [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=5092039C.60009@redhat.com \
--to=jasowang@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ernesto.martin@viasat.com \
--cc=haixiao@juniper.net \
--cc=krkumar2@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.