Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+net\-next\s+2\/3\]\s+ipvs\:\s+add\s+function\s+to\s+find\s+tunnels\s*$/: 4 ]

Total 4 documents matching your query.

1. Re: [PATCH net-next 2/3] ipvs: add function to find tunnels (score: 1)
Author: Simon Horman <horms@xxxxxxxxxxxx>
Date: Thu, 4 Apr 2019 12:13:18 +0200
Understood, I guess that minimising stack usage wins.
/html/lvs-devel/2019-04/msg00008.html (11,456 bytes)

2. Re: [PATCH net-next 2/3] ipvs: add function to find tunnels (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Wed, 3 Apr 2019 23:52:37 +0300 (EEST)
Hello, It was my initial option but then I decided to reduce the stack usage Regards -- Julian Anastasov <ja@xxxxxx>
/html/lvs-devel/2019-04/msg00005.html (10,575 bytes)

3. Re: [PATCH net-next 2/3] ipvs: add function to find tunnels (score: 1)
Author: Simon Horman <horms@xxxxxxxxxxxx>
Date: Wed, 3 Apr 2019 09:56:46 +0200
Hi Julian, Could we consider the following instead of casting? union nf_inet_addr raddr; ... raddr.ip = cih->daddr; ... est = ip_vs_find_tunnel(ipvs, AF_INET, &raddr, 0); ...
/html/lvs-devel/2019-04/msg00001.html (12,194 bytes)

4. [PATCH net-next 2/3] ipvs: add function to find tunnels (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Sun, 31 Mar 2019 13:26:20 +0300
Add ip_vs_find_tunnel() to match tunnel headers by family, address and optional port. Use it to properly find the tunnel real server used in received ICMP errors. Signed-off-by: Julian Anastasov <ja@
/html/lvs-devel/2019-03/msg00043.html (13,576 bytes)


This search system is powered by Namazu