Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+net\-next\s+06\/12\]\s+ipvs\:\s+optimize\s+dst\s+usage\s+for\s+real\s+server\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+net\-next\s+06\/12\]\s+ipvs\:\s+optimize\s+dst\s+usage\s+for\s+real\s+server\s*$/: 5 ]

Total 5 documents matching your query.

1. Re: [PATCH net-next 06/12] ipvs: optimize dst usage for real server (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Thu, 7 Mar 2013 02:14:00 +0200 (EET); Hello, May be it is possible, eg. by adding more arguments to __ip_vs_get_out_rt and moving all dst checks and icmp_send there. But there are some dst checks specific to the forwarding method, so I'm; /html/lvs-devel/2013-03/msg00020.html (13,164 bytes)
2. Re: [PATCH net-next 06/12] ipvs: optimize dst usage for real server (score: 1): Author: David Miller <davem@xxxxxxxxxxxxx>; Date: Wed, 06 Mar 2013 17:06:37 -0500 (EST); Both variants are starting to sound equally ugly :-) Let me ask about this situation in another way. IP input route lookup clients handle this transparently, even for routes with next-hop exceptions; /html/lvs-devel/2013-03/msg00019.html (12,272 bytes)
3. Re: [PATCH net-next 06/12] ipvs: optimize dst usage for real server (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Wed, 6 Mar 2013 23:58:09 +0200 (EET); Hello, This was my first thought but commit 27b75c95f1 (net: avoid RCU for NOCACHE dst) uses dst_hold for DST_NOCACHE dsts. IPVS wants to cache DST_NOCACHE entries (due to known-NH reasons) and later; /html/lvs-devel/2013-03/msg00018.html (14,058 bytes)
4. Re: [PATCH net-next 06/12] ipvs: optimize dst usage for real server (score: 1): Author: David Miller <davem@xxxxxxxxxxxxx>; Date: Wed, 06 Mar 2013 15:18:10 -0500 (EST); It think it's much cleaner to have the callers of route lookups do skb_set_dst_noref(). Then you don't need any new interfaces, and you therefore don't need to expose bits of the noref implementation; /html/lvs-devel/2013-03/msg00015.html (12,309 bytes)
5. [PATCH net-next 06/12] ipvs: optimize dst usage for real server (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Wed, 6 Mar 2013 10:42:16 +0200; Currently when forwarding requests to real servers we use dst_lock and atomic operations when cloning the dst_cache value. As the dst_cache value does not change most of the time it is better to use; /html/lvs-devel/2013-03/msg00007.html (54,522 bytes)

Current List: 1 - 5
Page: [1]