Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RFC\s+PATCHv2\s+2\/4\]\s+ipvs\:\s+use\s+kthreads\s+for\s+stats\s+estimation\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RFC\s+PATCHv2\s+2\/4\]\s+ipvs\:\s+use\s+kthreads\s+for\s+stats\s+estimation\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: [RFC PATCHv2 2/4] ipvs: use kthreads for stats estimation (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Fri, 9 Sep 2022 01:46:45 +0300 (EEST); Hello, OK, not fatal but this should be if (crow < IPVS_EST_NTICKS - 1) { Regards -- Julian Anastasov <ja@xxxxxx>; /html/lvs-devel/2022-09/msg00018.html (9,821 bytes)
2. [RFC PATCHv2 2/4] ipvs: use kthreads for stats estimation (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Fri, 9 Sep 2022 01:21:07 +0300; Estimating all entries in single list in timer context causes large latency with multiple rules. Spread the estimator structures in multiple chains and use kthread(s) for the estimation. Every chain; /html/lvs-devel/2022-09/msg00017.html (44,776 bytes)

Current List: 1 - 2
Page: [1]