Re: [2.6 PATCH] ipvs - make sure the timer expires on one cpu

netdev

Re: [2.6 PATCH] ipvs - make sure the timer expires on one cpu

To:	Julian Anastasov <ja@xxxxxx>
Subject:	Re: [2.6 PATCH] ipvs - make sure the timer expires on one cpu
From:	"David S. Miller" <davem@xxxxxxxxxx>
Date:	Tue, 11 Nov 2003 16:03:20 -0800
Cc:	netdev@xxxxxxxxxxx, wensong@xxxxxxxxxxxx
In-reply-to:	<Pine.LNX.4.44.0311111004540.1176-200000@xxxxxxxxxxxx>
References:	<Pine.LNX.4.44.0311110920420.1155-200000@xxxxxxxxxxxx> <Pine.LNX.4.44.0311111004540.1176-200000@xxxxxxxxxxxx>
Sender:	netdev-bounce@xxxxxxxxxxx

On Tue, 11 Nov 2003 10:07:17 +0200 (EET)
Julian Anastasov <ja@xxxxxx> wrote:

>       Ah, sorry. It is bad idea to set cp->timeout to 0. Please,
> better use the attached patch instead.

Applied, thanks Julian.

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[2.6 PATCH] ipvs - make sure the timer expires on one cpu, Julian Anastasov Re: [2.6 PATCH] ipvs - make sure the timer expires on one cpu, Julian Anastasov Re: [2.6 PATCH] ipvs - make sure the timer expires on one cpu, David S. Miller <=

Previous by Date:	Re: [PATCH] NET: Normalize jiffies reported to userspace, in neighbor management code, David S. Miller
Next by Date:	Re: Tigon3 5701 PCI-X recv performance problem, Andi Kleen
Previous by Thread:	Re: [2.6 PATCH] ipvs - make sure the timer expires on one cpu, Julian Anastasov
Next by Thread:	[PATCH] [bonding 2.4] fix creating/destroying the /proc/net/bonding dir, Amir Noam
Indexes:	[Date] [Thread] [Top] [All Lists]