Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+RFC\s+net\-next\]\s+net\:\s+ipvs\:\s+Adjust\s+gso_size\s+for\s+IPPROTO_TCP\s*$/: 10 ]

Total 10 documents matching your query.

1. Re: [PATCH RFC net-next] net: ipvs: Adjust gso_size for IPPROTO_TCP (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Wed, 6 Jun 2018 01:35:17 +0300 (EEST)
Hello, I was chasing other IPVS issues while preparing to finalize these changes. I plan to do tests this weekend and to submit my patch but without gso_size modifications. Can post patch for this ch
/html/lvs-devel/2018-06/msg00018.html (10,099 bytes)

2. Re: [PATCH RFC net-next] net: ipvs: Adjust gso_size for IPPROTO_TCP (score: 1)
Author: Martin KaFai Lau <kafai@xxxxxx>
Date: Tue, 5 Jun 2018 14:31:28 -0700
Hi Julian, Do you have a chance to work on the IPv6 side? Thanks, Martin -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx
/html/lvs-devel/2018-06/msg00017.html (9,458 bytes)

3. Re: [PATCH RFC net-next] net: ipvs: Adjust gso_size for IPPROTO_TCP (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Mon, 7 May 2018 20:00:22 +0300 (EEST)
Hello, if (ort->rt6i_flags & (RTF_CACHE | RTF_PCPU)) ort = ort->from; Sorry, my fault, I missed above re-assignment... WARN_ON_ONCE(ort->rt6i_flags & (RTF_CACHE | RTF_PCPU)); Aha, ok. I thought, only
/html/lvs-devel/2018-05/msg00012.html (12,204 bytes)

4. Re: [PATCH RFC net-next] net: ipvs: Adjust gso_size for IPPROTO_TCP (score: 1)
Author: Martin KaFai Lau <kafai@xxxxxx>
Date: Mon, 7 May 2018 09:22:31 -0700
hmm...I am not sure I follow this bits. Where is the warn? Note that "nrt6" and "from" are passed to rt6_insert_exception() instead of "rt6". The existing rt6_do_update_pmtu() looks correct. The mtu
/html/lvs-devel/2018-05/msg00011.html (13,369 bytes)

5. Re: [PATCH RFC net-next] net: ipvs: Adjust gso_size for IPPROTO_TCP (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Sat, 5 May 2018 15:58:25 +0300 (EEST)
Hello, I checked again the code and it looks like sockets are forced to use new exceptional route (RTF_CACHE/fnhe) via dst_check only when the PMTU update should move them away from old non-exception
/html/lvs-devel/2018-05/msg00007.html (12,218 bytes)

6. Re: [PATCH RFC net-next] net: ipvs: Adjust gso_size for IPPROTO_TCP (score: 1)
Author: David Ahern <dsahern@xxxxxxxxx>
Date: Thu, 3 May 2018 21:50:49 -0600
I agree; I think it is fine. A route is route. The IPVS use cases with local redirects are blurring the line with needs for local routes. -- To unsubscribe from this list: send the line "unsubscribe
/html/lvs-devel/2018-05/msg00006.html (13,003 bytes)

7. Re: [PATCH RFC net-next] net: ipvs: Adjust gso_size for IPPROTO_TCP (score: 1)
Author: Martin KaFai Lau <kafai@xxxxxx>
Date: Thu, 3 May 2018 00:01:25 -0700
IPv6 used not to create cache route for DST_HOST route which is a /128 route (that includes local /128 route). Because of this, it had a bug such that a PMTU for the DST_HOST route will trigger dst.o
/html/lvs-devel/2018-05/msg00003.html (13,465 bytes)

8. Re: [PATCH RFC net-next] net: ipvs: Adjust gso_size for IPPROTO_TCP (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Wed, 2 May 2018 22:30:32 +0300 (EEST)
Hello, Probably. I completely forgot the IPv6 part but as I don't know the IPv6 code enough, it may take some time to understand what can be the problem there... I'm not sure whether everything start
/html/lvs-devel/2018-05/msg00002.html (11,386 bytes)

9. Re: [PATCH RFC net-next] net: ipvs: Adjust gso_size for IPPROTO_TCP (score: 1)
Author: Martin KaFai Lau <kafai@xxxxxx>
Date: Wed, 2 May 2018 10:10:41 -0700
For IPv6, the 'if (rt6->rt6i_flags & RTF_LOCAL)' gate in __ip6_rt_update_pmtu() may need to be lifted also. -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a me
/html/lvs-devel/2018-05/msg00001.html (19,199 bytes)

10. Re: [PATCH RFC net-next] net: ipvs: Adjust gso_size for IPPROTO_TCP (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Wed, 2 May 2018 09:38:43 +0300 (EEST)
Hello, In the last week I analyzed the situation and found that just changes in route.c are able to solve the problems, at 99% :) I'm posting a separate patch for this. Here is what happens, I'm test
/html/lvs-devel/2018-05/msg00000.html (16,211 bytes)


This search system is powered by Namazu