Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+ipvs\:Fix\s+locking\s+requirements\s+in\s+the\s+function\s+ip_vs_unlink_service\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: [PATCH] ipvs:Fix locking requirements in the function ip_vs_unlink_service (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Sat, 12 Sep 2015 21:28:36 +0300 (EEST)
Hello, This function is called under __ip_vs_mutex, so there is single writer that modifies the configuration. As "readers" the schedulers access the configuration under rcu_read_lock (eg. called in
/html/lvs-devel/2015-09/msg00011.html (10,728 bytes)

2. Re: [PATCH] ipvs:Fix locking requirements in the function ip_vs_unlink_service (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Sat, 12 Sep 2015 09:20:21 +0300 (EEST)
Hello, BH locking is not needed anymore. Also, sched_lock is used by schedulers to protect only access to svc->sched_data fields. It seems the comment is outdated after commit ceec4c381681 ("ipvs: co
/html/lvs-devel/2015-09/msg00009.html (9,892 bytes)

Current List: 1 - 2
Page: [1]
This search system is powered by Namazu