Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*ip_vs_conn_expire_now\s+may\s+cause\s+timer\s+callback\s+runs\s+on\s+two\s+CPUs\s+for\s+a\s+same\s+session\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*ip_vs_conn_expire_now\s+may\s+cause\s+timer\s+callback\s+runs\s+on\s+two\s+CPUs\s+for\s+a\s+same\s+session\s*$/: 3 ]

Total 3 documents matching your query.

1. Re: ip_vs_conn_expire_now may cause timer callback runs on two CPUs for a same session (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Mon, 3 Oct 2016 10:49:03 +0300 (EEST); Hello, Yes, ip_vs_conn_unlink() can see refcnt=2 or more in which case it does not change refcnt (1->0) and conn remains hashed. But we have to start the timer again, so the pair atomic_inc+__ip_vs_c; /html/lvs-devel/2016-10/msg00002.html (9,818 bytes)
2. Re: ip_vs_conn_expire_now may cause timer callback runs on two CPUs for a same session (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Sun, 2 Oct 2016 21:30:59 +0300 (EEST); Hello, IIRC, timers can not be scheduled on multiple CPUs at the same time. They can be migrated to other CPUs but only if callback is not running. __mod_timer() checks if the callback is running (ba; /html/lvs-devel/2016-10/msg00001.html (11,386 bytes)
3. ip_vs_conn_expire_now may cause timer callback runs on two CPUs for a same session (score: 1): Author: HePeng <xnhp0320@xxxxxxxxxx>; Date: Sun, 2 Oct 2016 23:59:49 +0800; Hi, I am a newbie to IPVS. I read the code of ipvs in 3.10 kernel, and think the the implementation of *ip_vs_expire_now* may cause timer callback runs on two CPUs for a same session. CPU 0 CPU 1 CPU; /html/lvs-devel/2016-10/msg00000.html (8,981 bytes)

Current List: 1 - 3
Page: [1]