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

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Julian Anastasov
Date: Wednesday, September 1, 2010 - 5:16 pm

Hello,

On Wed, 1 Sep 2010, Simon Horman wrote:


	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.

Regards

--
Julian Anastasov <ja@ssi.bg>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[RFC] ipvs: Keep track of backlog connections, Sven Wegener, (Tue Aug 31, 5:19 am)
Re: [RFC] ipvs: Keep track of backlog connections, Simon Horman, (Tue Aug 31, 7:57 pm)
Re: [RFC] ipvs: Keep track of backlog connections, Julian Anastasov, (Wed Sep 1, 1:32 am)
Re: [RFC] ipvs: Keep track of backlog connections, Simon Horman, (Wed Sep 1, 6:28 am)
Re: [RFC] ipvs: Keep track of backlog connections, Julian Anastasov, (Wed Sep 1, 5:16 pm)
Re: [RFC] ipvs: Keep track of backlog connections, Simon Horman, (Wed Sep 1, 6:48 pm)