On Thu, Jul 26, 2007 at 10:31:20AM +0200, Ingo Molnar wrote: ... > yeah. The patch below enables sw-resend on x86, to test the theory > whether the APIC-driven hardware-vector-resend code has some problem. I think Marcin is using x86_64 (Athlon 64) yet. Jarek P. - 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/
- Follow-Ups:
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Ingo Molnar <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- References:
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: "Marcin Ślusarz" <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Ingo Molnar <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Ingo Molnar <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Linus Torvalds <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Ingo Molnar <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Thomas Gleixner <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: "Marcin Ślusarz" <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Jarek Poplawski <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Thomas Gleixner <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Ingo Molnar <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- Prev by Date: [PATCH trivial v2] add includes to scsi_transport_iscsi.h
- Next by Date: [patch] sched: make cpu_clock() not use the rq clock
- Previous by thread: Re: 2.6.20->2.6.21 - networking dies after random time
- Next by thread: Re: 2.6.20->2.6.21 - networking dies after random time
- Index(es):
 |