public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <prh@gotadsl.co.uk>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Unexpected side effect of GCC 4
Date: Sun, 5 Nov 2006 08:45:42 +0000	[thread overview]
Message-ID: <200611050845.42865.prh@gotadsl.co.uk> (raw)

I have a firewall between my ADSL modem and my local network (running 
Gentoo, naturally), and I use it as an rsync server for portage on the 
network. Specifically, the firewall runs emerge --sync in a cron job every 
morning before I get up, then I synchronise my laptop and desktop systems 
from that at my convenience.

The rsync phase of update over the local network has been extremely slow; I 
couldn't get traffic flowing faster than about 30 - 40 kBps on average, and 
the hub showed tremendous numbers of collisions. I did manage to speed it 
up a bit by changing the /usr/portage partition on the server to reiserfs, 
but that improvement seemed to go away again. Meanwhile, other traffic over 
the network went at full speed, about 270 kBps, with only the occasional 
collision.

Now that I've finally managed to build a full system using GCC 4.1.1 on the 
workstation, I find its rsync traffic has leapt to full speed with no 
collisions to speak of. I'm not complaining, mind, but this is a puzzle. As 
far as I know I haven't changed anything else - certainly the firewall box 
has been running continuously throughout.

The speeds I mention are as shown by gkrellm (a very useful utility). The 
network drivers are a module on the workstation (tg3) and built-in on the 
firewall (8139too). The CFLAGS are "-O2 -march=k8 -pipe" on the firewall 
and the set offered by Duncan recently on the workstation.

Any ideas, anyone?

-- 
Rgds
Peter
-- 
gentoo-amd64@gentoo.org mailing list



             reply	other threads:[~2006-11-05  8:48 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-05  8:45 Peter Humphrey [this message]
2006-11-05 10:12 ` [gentoo-amd64] Re: Unexpected side effect of GCC 4 Duncan
2006-11-05 11:50   ` Peter Humphrey
2006-11-05 12:10     ` Peter Humphrey
2006-11-06  8:17       ` Duncan
2006-11-06  8:29         ` Hemmann, Volker Armin
2006-11-06 15:57           ` Duncan
2006-11-06  7:50     ` Duncan
2006-11-06  8:48       ` Peter Humphrey
2006-11-06 16:01         ` Duncan
2006-11-06 16:06         ` Peter Humphrey
2006-11-06  8:41     ` Duncan
2006-11-06 10:47       ` Hemmann, Volker Armin
2006-11-06 11:48         ` Peter Humphrey
2006-11-06 12:05           ` Hemmann, Volker Armin
2006-11-06 12:49             ` Jack Lloyd
2006-11-06 12:59               ` Hemmann, Volker Armin
2006-11-06 13:06                 ` Jack Lloyd
2006-11-06 15:06                 ` Peter Humphrey
2006-11-06 11:44       ` Peter Humphrey
2006-11-06 15:51         ` Duncan
2006-11-08 11:19           ` Peter Humphrey
2006-11-08 15:17             ` Duncan
2006-11-10 10:14               ` Peter Humphrey
2006-11-05 13:24   ` Hemmann, Volker Armin
2006-11-05 23:26     ` Duncan
2006-11-08 10:14 ` [gentoo-amd64] " Peter Humphrey
2006-11-08 11:06   ` [gentoo-amd64] " Duncan

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=200611050845.42865.prh@gotadsl.co.uk \
    --to=prh@gotadsl.co.uk \
    --cc=gentoo-amd64@lists.gentoo.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