[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20071219134805.GC21282@elte.hu>
Date: Wed, 19 Dec 2007 14:48:07 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Michael Buesch <mb@...sch.de>
Cc: bcm43xx-dev@...ts.berlios.de,
Larry Finger <larry.finger@...inger.net>,
mvtodevnull@...il.com, Daniel Walker <dwalker@...sta.com>,
akpm@...ux-foundation.org, Ray Lee <ray-lk@...rabbit.org>,
n <odie@...aau.dk>,
SimonHolmThøgerse@...l.berlios.de,
matthias.kaehlcke@...il.com, linux-kernel@...r.kernel.org,
jonathan@...masters.org, kjwinchester@...il.com, linux@...mer.net
Subject: Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore
to mutex
* Michael Buesch <mb@...sch.de> wrote:
> On Wednesday 19 December 2007 09:11:02 Larry Finger wrote:
> > >
> > > or could tsc being marked as unstable have anything to do with the
> > > speed of network transfers?
> >
> > Absolutely not.
>
> Well, if the clocksource of the machine is unstable it _can_ cause all
> kinds of weird things. If you think something is broken in the tsc
> stuff, please switch to using another clocksource.
also, if it gets marked unstable (which is typical on laptops) then the
kernel switches to a more stable, non-TSC clocksource automatically.
(hpet or pit)
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists