[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bridge-utils in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894608
Mike Imelfort, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test the latest upstream kernel available
following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow
additional
Mike Imelfort, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test the latest upstream kernel available
following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow
additional
Marking it invalid against bridge-utils as the tool used to setup the bridge
isn't the problem, it's most likely either a kernel bug or a configuration
problem.
I personally reproduce similar bottlenecks in the past and Simon's suggestion
usually helps quite a lot (if CPU bound).
** Changed
Marking it invalid against bridge-utils as the tool used to setup the bridge
isn't the problem, it's most likely either a kernel bug or a configuration
problem.
I personally reproduce similar bottlenecks in the past and Simon's suggestion
usually helps quite a lot (if CPU bound).
** Changed
** Tags added: needs-upstream-testing
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/894608
Title:
Implementing a bridge slows 10G network
To manage notifications about this
** Tags added: needs-upstream-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894608
Title:
Implementing a bridge slows 10G network
To manage notifications about this bug go to:
@Michael, I haven't tried to reproduce your issue but maybe some of the
bridge bottleneck comes from the netfilter hooks ?
Maybe you could try setting those sysctl keys :
net.bridge.bridge-nf-call-iptables=0
net.bridge.bridge-nf-call-ip6tables=0
net.bridge.bridge-nf-call-arptables=0
That is
@Michael, I haven't tried to reproduce your issue but maybe some of the
bridge bottleneck comes from the netfilter hooks ?
Maybe you could try setting those sysctl keys :
net.bridge.bridge-nf-call-iptables=0
net.bridge.bridge-nf-call-ip6tables=0
net.bridge.bridge-nf-call-arptables=0
That is
Thanks, Michael - that appears to show that the window size has nothing
to do with it.
At this point, I can only suggest watching 'top' while the benchmark is
running, to see if the cpu is a bottleneck when you are getting the poor
results. Hopefully someone more knowledgeable will chime in with
Thanks, Michael - that appears to show that the window size has nothing
to do with it.
At this point, I can only suggest watching 'top' while the benchmark is
running, to see if the cpu is a bottleneck when you are getting the poor
results. Hopefully someone more knowledgeable will chime in with
Oops sorry, Here tis'
whitlam:~$ iperf -sm -w 80k
Server listening on TCP port 5001
TCP window size: 160 KByte (WARNING: requested 80.0 KByte)
[ 4] local 10.168.48.14 port
Oops sorry, Here tis'
whitlam:~$ iperf -sm -w 80k
Server listening on TCP port 5001
TCP window size: 160 KByte (WARNING: requested 80.0 KByte)
[ 4] local 10.168.48.14 port
Could you show the results? (I'm curious what it then reports as TCP
window size)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/894608
Title:
Implementing a bridge slows 10G
Could you show the results? (I'm curious what it then reports as TCP
window size)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894608
Title:
Implementing a bridge slows 10G network
To manage
I have '-w 80k' now. It's still the same...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/894608
Title:
Implementing a bridge slows 10G network
To manage notifications about
I have '-w 80k' now. It's still the same...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894608
Title:
Implementing a bridge slows 10G network
To manage notifications about this bug go to:
Those look normal and the same as on my systems...
Could you try running iperf with the added '-w 80k' argument?
** Changed in: bridge-utils (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Those look normal and the same as on my systems...
Could you try running iperf with the added '-w 80k' argument?
** Changed in: bridge-utils (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Here are the results:
(Fraser is the one with bridge utils installed)
fraser:~$ cat /proc/sys/net/ipv4/tcp_rmem
409687380 4194304
fraser:~$ cat/proc/sys/net/ipv4/tcp_wmem
409616384 4194304
whitlam:~$ cat /proc/sys/net/ipv4/tcp_rmem
409687380 4194304
whitlam:~$ cat
Here are the results:
(Fraser is the one with bridge utils installed)
fraser:~$ cat /proc/sys/net/ipv4/tcp_rmem
409687380 4194304
fraser:~$ cat/proc/sys/net/ipv4/tcp_wmem
409616384 4194304
whitlam:~$ cat /proc/sys/net/ipv4/tcp_rmem
409687380 4194304
whitlam:~$ cat
Thanks, Mike. I tried to reproduce this with two lucid machines. With both
not using bridges, I got:
Client connecting to 10.55.55.5, TCP port 5001
TCP window size: 166 KByte (default)
Thanks, Mike. I tried to reproduce this with two lucid machines. With both
not using bridges, I got:
Client connecting to 10.55.55.5, TCP port 5001
TCP window size: 166 KByte (default)
Thanks for getting back to me.
Here is brctl show output:
$ brctl show
bridge name bridge id STP enabled interfaces
br0 8000.0010187ee074 no eth4
and ip link:
$ ip link
1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN
apport information
** Tags added: apport-collected
** Description changed:
Installing bridge-utils and then setting up a bridge in
/etc/netwrok/interfaces decimates my netwrok speed. Uninstalling the
package and doing a reboot restores the speed.
This bug was originally posted here:
I just wanted to make sure that I can reproduce this from scratch, for
anyone who's interested...
Fresh install from 10.04.3 CD, choosing openssh-server as the only
extra package
$ sudo -s
$ apt-get update
$ apt-get dist-upgrade
$ aptitude install iperf
...
test network speed - all OK
...
$
Thanks for getting back to me.
Here is brctl show output:
$ brctl show
bridge name bridge id STP enabled interfaces
br0 8000.0010187ee074 no eth4
and ip link:
$ ip link
1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN
apport information
** Tags added: apport-collected
** Description changed:
Installing bridge-utils and then setting up a bridge in
/etc/netwrok/interfaces decimates my netwrok speed. Uninstalling the
package and doing a reboot restores the speed.
This bug was originally posted here:
I just wanted to make sure that I can reproduce this from scratch, for
anyone who's interested...
Fresh install from 10.04.3 CD, choosing openssh-server as the only
extra package
$ sudo -s
$ apt-get update
$ apt-get dist-upgrade
$ aptitude install iperf
...
test network speed - all OK
...
$
Thanks for reporting this bug. I've marked it as also affecting the
kernel as the bridge driver seems most likely to be the problem.
** Changed in: bridge-utils (Ubuntu)
Importance: Undecided = Medium
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You
Several sources suggest that turning odd tso, and perhaps also sg and
tx, might help. Could you try
sudo ethtool -K eth4 tso off
sudo ethtool -K eth4 sg off
sudo ethtool -K eth4 tx off
and try again?
Also, could you show the result of 'brctl show' and 'ip link'?
** Changed in: bridge-utils
Thanks for reporting this bug. I've marked it as also affecting the
kernel as the bridge driver seems most likely to be the problem.
** Changed in: bridge-utils (Ubuntu)
Importance: Undecided = Medium
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You
Several sources suggest that turning odd tso, and perhaps also sg and
tx, might help. Could you try
sudo ethtool -K eth4 tso off
sudo ethtool -K eth4 sg off
sudo ethtool -K eth4 tx off
and try again?
Also, could you show the result of 'brctl show' and 'ip link'?
** Changed in: bridge-utils
** Description changed:
Installing bridge-utils and then setting up a bridge in
/etc/netwrok/interfaces decimates my netwrok speed. Uninstalling the
package and doing a reboot restores the speed.
This bug was originally posted here:
https://bugs.launchpad.net/qemu/+bug/861141 but I
** Description changed:
Installing bridge-utils and then setting up a bridge in
/etc/netwrok/interfaces decimates my netwrok speed. Uninstalling the
package and doing a reboot restores the speed.
This bug was originally posted here:
https://bugs.launchpad.net/qemu/+bug/861141 but I
36 matches
Mail list logo
