Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+ipvs\-next\]\s+ipvs\:\s+avoid\s+indirect\s+calls\s+when\s+calculating\s+checksums\s*$/: 3 ]

Total 3 documents matching your query.

1. Re: [PATCH ipvs-next] ipvs: avoid indirect calls when calculating checksums (score: 1)
Author: Simon Horman <horms@xxxxxxxxxxxx>
Date: Wed, 23 Jan 2019 13:50:56 +0100
Likewise, Pablo could you consider applying this to nf-next? Acked-by: Simon Horman <horms@xxxxxxxxxxxx>
/html/lvs-devel/2019-01/msg00023.html (22,683 bytes)

2. Re: [PATCH ipvs-next] ipvs: avoid indirect calls when calculating checksums (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Sun, 20 Jan 2019 14:11:31 +0200 (EET)
Hello, Looks good to me, thanks! Acked-by: Julian Anastasov <ja@xxxxxx> Regards -- Julian Anastasov <ja@xxxxxx>
/html/lvs-devel/2019-01/msg00018.html (21,414 bytes)

3. [PATCH ipvs-next] ipvs: avoid indirect calls when calculating checksums (score: 1)
Author: Matteo Croce <mcroce@xxxxxxxxxx>
Date: Sat, 19 Jan 2019 15:22:38 +0100
The function pointer ip_vs_protocol->csum_check is only used in protocol specific code, and never in the generic one. Remove the function pointer from struct ip_vs_protocol and call the checksum func
/html/lvs-devel/2019-01/msg00016.html (18,510 bytes)


This search system is powered by Namazu