Re: Network performance degradation from 2.6.11.12 to 2.6.16.20

Andi Kleen
2006-09-18T08:36:07Z

"Vladimir B. Savkin" <master@sectorb.msk.ru> writes:

> On Mon, Jun 19, 2006 at 05:24:31PM +0200, Andi Kleen wrote:
> >
> > > If you use "pmtmr" try to reboot with kernel option "clock=tsc".
> >
> > That's dangerous advice - when the system choses not to use
> > TSC it often has a reason.
>
> I just found out that TSC clocksource is not implemented on x86-64.
> Kernel version 2.6.18-rc7, is it true?

The x86-64 timer subsystems currently doesn't have clocksources
at all, but it supports TSC and some other timers.

>
> I've also had experience of unsychronized TSC on dual-core Athlon,
> but it was cured by idle=poll.

You can use that, but it will make your system run quite hot
and cost you a lot of powe^wmoney.

> It seems that dhcpd3 makes the box timestamping incoming packets,
> killing the performance. I think that combining router and DHCP server
> on a same box is a legitimate situation, isn't it?

Yes. Good point. DHCP is broken and needs to be fixed. Can you
send a bug report to the DHCP maintainers?

iirc the problem used to be that RAW sockets didn't do something
they need them to do. Maybe we can fix that now.

If that's not possible we can probably add a ioctl or similar
to disable time stamping for packet sockets (DHCP shouldn't really
need a fine grained time stamp). dhcpcd would need to use that then.

Keep me updated what they say.

-Andi