From: Wolfgang Rosner <wrosner@tirnet.de>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: One way TCP bottleneck over 6 x Gbit tecl aggregated link // Kernel issue
Date: Mon, 23 Mar 2015 10:05:01 +0100 [thread overview]
Message-ID: <201503231005.02195.wrosner@tirnet.de> (raw)
In-Reply-To: <1427077997.25985.59.camel@edumazet-glaptop2.roam.corp.google.com>
Am Montag, 23. März 2015 03:33:17 schrieb Eric Dumazet:
> On Mon, 2015-03-23 at 01:57 +0100, Wolfgang Rosner wrote:
> > Are you ready to assist me on this track?
>
> First check if the problem is already solved, using this git tree ?
>
> http://git.kernel.org/cgit/linux/kernel/git/davem/net.git
Is it OK to use this 3.19 tag?
https://kernel.googlesource.com/pub/scm/linux/kernel/git/davem/net.git/+/v3.19
I see that head is v4.0-rc4
I'm afraid that this might break other things.
I think of aufs, which I need to get my clients nfsroot booted.
Without clients, I can't iperf the teql link.
I have to admit that I'm not the master of this git beast.
But I'm working my way, somehow...
Wolfgang Rosner
next prev parent reply other threads:[~2015-03-23 9:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 0:10 One way TCP bottleneck over 6 x Gbit tecl aggregated link Wolfgang Rosner
2015-03-21 1:15 ` Eric Dumazet
[not found] ` <201503220912.39912.wrosner@tirnet.de>
[not found] ` <1427020159.25985.43.camel@edumazet-glaptop2.roam.corp.google.com>
2015-03-22 15:14 ` Wolfgang Rosner
2015-03-22 16:54 ` Eric Dumazet
2015-03-22 20:47 ` Wolfgang Rosner
2015-03-23 0:57 ` One way TCP bottleneck over 6 x Gbit tecl aggregated link // Kernel issue Wolfgang Rosner
2015-03-23 2:33 ` Eric Dumazet
2015-03-23 9:05 ` Wolfgang Rosner [this message]
2015-03-23 9:25 ` Zimmermann, Alexander
2015-03-23 13:54 ` Wolfgang Rosner
2015-03-24 12:59 ` Zimmermann, Alexander
2015-03-26 19:34 ` Wolfgang Rosner
2015-03-27 18:46 ` Wolfgang Rosner
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=201503231005.02195.wrosner@tirnet.de \
--to=wrosner@tirnet.de \
--cc=eric.dumazet@gmail.com \
--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