Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore to mutex

* Michael Buesch <[email protected]> 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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH 1/3] ps3: vuart: fix error path locking
    • From: Daniel Walker <[email protected]>
  • Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore to mutex
    • From: [email protected]
  • Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore to mutex
    • From: Larry Finger <[email protected]>

• Prev by Date: Re: [PATCH] finish processor.h integration
• Next by Date: [build bug, 2.6.24-rc5] drivers/isdn/built-in.o: No such file
• Previous by thread: Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore to mutex
• Next by thread: Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore to mutex
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]