Re: [RFC] ipvs: Keep track of backlog connections

To: Simon Horman <horms@xxxxxxxxxxxx>
Subject: Re: [RFC] ipvs: Keep track of backlog connections
Cc: Sven Wegener <sven.wegener@xxxxxxxxxxx>, lvs-devel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxxxxxx, Wensong Zhang <wensong@xxxxxxxxxxxx>
From: Julian Anastasov <ja@xxxxxx>
Date: Thu, 2 Sep 2010 03:16:40 +0300 (EEST)

On Wed, 1 Sep 2010, Simon Horman wrote:

> On the kernel-side of things, internally it should be easy
> enough to either expand flags or add a new element to the structure.
> So it seems to me that the problem is the kernel/user-space interface.
> And if that is the case, I think the best idea is to just use
> the netlink interface for all new configuration options and have
> new features unsupported through the old, legacy, ioctl interface.

        No, there should be no problem with the interface,
it already uses 32 bits. We should change only cp->flags
to 32 bits and new flags should go after bit 16 if they
are not needed for sync. Some flags can be changed safely,
for example, IP_VS_CONN_F_SYNC: it is not used by ipvsadm,
it is set only in backup, so it can be moved after bit 16.
May be another idea is to create 2nd version for the
struct ip_vs_sync_conn to support more features.


Julian Anastasov <ja@xxxxxx>
To unsubscribe from this list: send the line "unsubscribe lvs-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at

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