LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: invoke scheduler for every received packet

To: Julian Anastasov <ja@xxxxxx>
Subject: Re: invoke scheduler for every received packet
Cc: "LinuxVirtualServer.org users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
From: Viktor Matic <viktor@xxxxxxxxxxxx>
Date: Sat, 15 Jul 2006 11:08:41 +0200
Hello,
>On Sat, 2006-07-15 at 11:31 +0300, Julian Anastasov wrote:
>       Hello,
> 
> On Fri, 14 Jul 2006, Viktor Matic wrote:
> 
> > I'm far from expertise for LVS codebase. But while playing with OPS I've
> > encountered odd behavior on bigger load I've notice increased memory
> > consumption. I have added some logging to code and it seemed to me that
> > function [void ip_vs_conn_expire_now(struct ip_vs_conn *cp)] doesn't do
> > it's job. It is possible that I've miss-interpreted something.
> > So in my opinion it would be much better to avoid timer creation and
> > connection hashing. Actually it is not needed in this case. Of course if
> > it doesn't ruin complete concept.
> 
>       I think, you are using incomplete patch (may be because
> there is no complete patch) for 2.6. What i know as last version is:
> 
> http://marc.theaimsgroup.com/?l=linux-virtual-server&m=112800257026121&w=2
> 
>       but it needs some fixes (ip_vs_conn_expire_now should not
> be called):
> 
> http://marc.theaimsgroup.com/?l=linux-virtual-server&m=112806105113957&w=2
> 
>       I personally don't have 2.6 version.
Yes, now I can see difference in the ip_vs_conn_put function. I was not aware 
of this change. 
But, still I do not understand why ip_vs_conn_expire_now in older patch
do not expire connection? 

Thanks,

Viktor



<Prev in Thread] Current Thread [Next in Thread>