From: David Ahern <dsa@cumulusnetworks.com>
To: Simon Xiao <sixiao@microsoft.com>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: David Miller <davem@davemloft.net>,
KY Srinivasan <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>
Subject: Re: linux-next network throughput performance regression
Date: Fri, 6 Nov 2015 14:30:08 -0700 [thread overview]
Message-ID: <563D1BE0.2070107@cumulusnetworks.com> (raw)
In-Reply-To: <CY1PR03MB13763CB0C0A9C822660E248AC4280@CY1PR03MB1376.namprd03.prod.outlook.com>
On 11/6/15 2:18 PM, Simon Xiao wrote:
> The .config file used to build linux-next kernel is attached to this mail.
Thanks.
Failed to notice this on the first response; my brain filled in. Why
linux-next tree? Can you try net-next which is more relevant for this
mailing list, post the top commit id and config file used?
next prev parent reply other threads:[~2015-11-06 21:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 20:31 linux-next network throughput performance regression Simon Xiao
2015-11-06 20:31 ` Simon Xiao
2015-11-06 20:45 ` David Ahern
2015-11-06 21:18 ` Simon Xiao
2015-11-06 21:18 ` Simon Xiao
2015-11-06 21:30 ` David Ahern [this message]
2015-11-07 19:35 ` Eric Dumazet
2015-11-07 19:35 ` Eric Dumazet
2015-11-07 19:50 ` Eric Dumazet
2015-11-07 19:50 ` Eric Dumazet
2015-11-09 20:23 ` Simon Xiao
2015-11-09 20:23 ` Simon Xiao
2015-11-09 23:04 ` Eric Dumazet
2015-11-09 23:04 ` Eric Dumazet
2015-11-09 2:39 ` Dexuan Cui
2015-11-09 2:39 ` Dexuan Cui
2015-11-09 2:52 ` David Miller
2015-11-09 2:52 ` David Miller
2015-11-09 3:11 ` Dexuan Cui
2015-11-09 3:11 ` Dexuan Cui
2015-11-09 3:23 ` David Miller
2015-11-09 3:23 ` David Miller
2015-11-09 3:31 ` Dexuan Cui
2015-11-09 3:31 ` Dexuan Cui
2015-11-09 5:30 ` Tom Herbert
2015-11-09 3:32 ` Dave Airlie
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=563D1BE0.2070107@cumulusnetworks.com \
--to=dsa@cumulusnetworks.com \
--cc=davem@davemloft.net \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sixiao@microsoft.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.