From: David Miller <davem@davemloft.net>
To: david.stevens@oracle.com
Cc: netdev@vger.kernel.org, sowmini.varadhan@oracle.com,
raghuram.kothakota@oracle.com
Subject: Re: [PATCHv9 net-next 0/4] sunvnet: add jumbo frames support
Date: Tue, 30 Sep 2014 17:11:29 -0400 (EDT) [thread overview]
Message-ID: <20140930.171129.303142714967964225.davem@davemloft.net> (raw)
In-Reply-To: <5429EFA3.9050304@oracle.com>
From: David L Stevens <david.stevens@oracle.com>
Date: Mon, 29 Sep 2014 19:47:47 -0400
> This patch set updates the sunvnet driver to version 1.6 of the VIO protocol
> to support per-port exchange of MTU information and allow non-standard MTU
> sizes, including jumbo frames.
>
> Using large MTUs shows a nearly 5X throughput improvement Linux-Solaris
> and > 10X throughput improvement Linux-Linux.
Looks great, applied to net-next, and as I mentioned I'll push the
arch/sparc bits from patch #1 into the sparc tree too.
prev parent reply other threads:[~2014-09-30 21:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 23:47 [PATCHv9 net-next 0/4] sunvnet: add jumbo frames support David L Stevens
2014-09-30 21:11 ` David Miller [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=20140930.171129.303142714967964225.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=david.stevens@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=raghuram.kothakota@oracle.com \
--cc=sowmini.varadhan@oracle.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 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).