From: Stephen Hemminger <shemminger@vyatta.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC net-next] tun: implement BQL
Date: Tue, 13 Nov 2012 14:39:47 -0800 [thread overview]
Message-ID: <20121113143947.35278b84@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <20121113.171939.1673751173342429141.davem@davemloft.net>
On Tue, 13 Nov 2012 17:19:39 -0500 (EST)
David Miller <davem@davemloft.net> wrote:
> From: Stephen Hemminger <shemminger@vyatta.com>
> Date: Mon, 12 Nov 2012 13:22:41 -0800
>
> > Add multiqueue BQL to tap device. Tested with VPN, doesn't have a big impact,
> > most likely because there is little queueing occuring at TAP device except
> > under case of forwarding.
> >
> > Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
>
> I think unless we can show it making an impact in a normal
> usage scenerio, we should leave it alone for now.
Agreed, that is why I submitted as RFC.
prev parent reply other threads:[~2012-11-13 22:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 21:22 [RFC net-next] tun: implement BQL Stephen Hemminger
2012-11-13 22:19 ` David Miller
2012-11-13 22:39 ` Stephen Hemminger [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=20121113143947.35278b84@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--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).