From: Julian Anastasov <ja@ssi.bg>
To: Simon Horman <horms@verge.net.au>
Cc: lvs-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH net-next 01/19] ipvs: change ip_vs_sched_lock to mutex
Date: Fri, 22 Mar 2013 11:46:36 +0200 [thread overview]
Message-ID: <1363945614-11752-2-git-send-email-ja@ssi.bg> (raw)
In-Reply-To: <1363945614-11752-1-git-send-email-ja@ssi.bg>
The global list with schedulers ip_vs_schedulers
is accessed only from user context - configuration and
scheduler module [un]registration. Use ip_vs_sched_mutex
instead.
Signed-off-by: Julian Anastasov <ja@ssi.bg>
---
net/netfilter/ipvs/ip_vs_sched.c | 24 ++++++++++++------------
1 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/net/netfilter/ipvs/ip_vs_sched.c b/net/netfilter/ipvs/ip_vs_sched.c
index d6bf20d..7f11d3d 100644
--- a/net/netfilter/ipvs/ip_vs_sched.c
+++ b/net/netfilter/ipvs/ip_vs_sched.c
@@ -35,8 +35,8 @@ EXPORT_SYMBOL(ip_vs_scheduler_err);
*/
static LIST_HEAD(ip_vs_schedulers);
-/* lock for service table */
-static DEFINE_SPINLOCK(ip_vs_sched_lock);
+/* semaphore for schedulers */
+static DEFINE_MUTEX(ip_vs_sched_mutex);
/*
@@ -92,7 +92,7 @@ static struct ip_vs_scheduler *ip_vs_sched_getbyname(const char *sched_name)
IP_VS_DBG(2, "%s(): sched_name \"%s\"\n", __func__, sched_name);
- spin_lock_bh(&ip_vs_sched_lock);
+ mutex_lock(&ip_vs_sched_mutex);
list_for_each_entry(sched, &ip_vs_schedulers, n_list) {
/*
@@ -106,14 +106,14 @@ static struct ip_vs_scheduler *ip_vs_sched_getbyname(const char *sched_name)
}
if (strcmp(sched_name, sched->name)==0) {
/* HIT */
- spin_unlock_bh(&ip_vs_sched_lock);
+ mutex_unlock(&ip_vs_sched_mutex);
return sched;
}
if (sched->module)
module_put(sched->module);
}
- spin_unlock_bh(&ip_vs_sched_lock);
+ mutex_unlock(&ip_vs_sched_mutex);
return NULL;
}
@@ -192,10 +192,10 @@ int register_ip_vs_scheduler(struct ip_vs_scheduler *scheduler)
/* increase the module use count */
ip_vs_use_count_inc();
- spin_lock_bh(&ip_vs_sched_lock);
+ mutex_lock(&ip_vs_sched_mutex);
if (!list_empty(&scheduler->n_list)) {
- spin_unlock_bh(&ip_vs_sched_lock);
+ mutex_unlock(&ip_vs_sched_mutex);
ip_vs_use_count_dec();
pr_err("%s(): [%s] scheduler already linked\n",
__func__, scheduler->name);
@@ -208,7 +208,7 @@ int register_ip_vs_scheduler(struct ip_vs_scheduler *scheduler)
*/
list_for_each_entry(sched, &ip_vs_schedulers, n_list) {
if (strcmp(scheduler->name, sched->name) == 0) {
- spin_unlock_bh(&ip_vs_sched_lock);
+ mutex_unlock(&ip_vs_sched_mutex);
ip_vs_use_count_dec();
pr_err("%s(): [%s] scheduler already existed "
"in the system\n", __func__, scheduler->name);
@@ -219,7 +219,7 @@ int register_ip_vs_scheduler(struct ip_vs_scheduler *scheduler)
* Add it into the d-linked scheduler list
*/
list_add(&scheduler->n_list, &ip_vs_schedulers);
- spin_unlock_bh(&ip_vs_sched_lock);
+ mutex_unlock(&ip_vs_sched_mutex);
pr_info("[%s] scheduler registered.\n", scheduler->name);
@@ -237,9 +237,9 @@ int unregister_ip_vs_scheduler(struct ip_vs_scheduler *scheduler)
return -EINVAL;
}
- spin_lock_bh(&ip_vs_sched_lock);
+ mutex_lock(&ip_vs_sched_mutex);
if (list_empty(&scheduler->n_list)) {
- spin_unlock_bh(&ip_vs_sched_lock);
+ mutex_unlock(&ip_vs_sched_mutex);
pr_err("%s(): [%s] scheduler is not in the list. failed\n",
__func__, scheduler->name);
return -EINVAL;
@@ -249,7 +249,7 @@ int unregister_ip_vs_scheduler(struct ip_vs_scheduler *scheduler)
* Remove it from the d-linked scheduler list
*/
list_del(&scheduler->n_list);
- spin_unlock_bh(&ip_vs_sched_lock);
+ mutex_unlock(&ip_vs_sched_mutex);
/* decrease the module use count */
ip_vs_use_count_dec();
--
1.7.3.4
next prev parent reply other threads:[~2013-03-22 9:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 9:46 [PATCH net-next 00/19] IPVS optimizations, part 2 Julian Anastasov
2013-03-22 9:46 ` Julian Anastasov [this message]
2013-03-22 9:46 ` [PATCH net-next 02/19] ipvs: preparations for using rcu in schedulers Julian Anastasov
2013-03-22 9:46 ` [PATCH net-next 03/19] ipvs: add ip_vs_dest_hold and ip_vs_dest_put Julian Anastasov
2013-03-22 9:46 ` [PATCH net-next 04/19] ipvs: convert dh scheduler to rcu Julian Anastasov
2013-03-22 9:46 ` [PATCH net-next 05/19] ipvs: convert lblc " Julian Anastasov
2013-03-22 9:46 ` [PATCH net-next 06/19] ipvs: convert lblcr " Julian Anastasov
2013-03-22 9:46 ` [PATCH net-next 07/19] ipvs: convert lc " Julian Anastasov
2013-03-22 9:46 ` [PATCH net-next 08/19] ipvs: convert nq " Julian Anastasov
2013-03-22 9:46 ` [PATCH net-next 09/19] ipvs: convert rr " Julian Anastasov
2013-03-22 9:46 ` [PATCH net-next 10/19] ipvs: convert sed " Julian Anastasov
2013-03-22 9:46 ` [PATCH net-next 11/19] ipvs: convert sh " Julian Anastasov
2013-03-22 9:46 ` [PATCH net-next 12/19] ipvs: convert wlc " Julian Anastasov
2013-03-22 9:46 ` [PATCH net-next 13/19] ipvs: convert wrr " Julian Anastasov
2013-03-22 9:46 ` [PATCH net-next 14/19] ipvs: reorganize dest trash Julian Anastasov
2013-03-22 9:46 ` [PATCH net-next 15/19] ipvs: do not expect result from done_service Julian Anastasov
2013-03-22 9:46 ` [PATCH net-next 16/19] ipvs: convert sched_lock to spin lock Julian Anastasov
2013-03-22 9:46 ` [PATCH net-next 17/19] ipvs: convert dests to rcu Julian Anastasov
2013-03-22 9:46 ` [PATCH net-next 18/19] ipvs: convert services " Julian Anastasov
2013-03-22 9:46 ` [PATCH net-next 19/19] ipvs: do not disable bh for long time Julian Anastasov
2013-03-28 5:41 ` [PATCH net-next 00/19] IPVS optimizations, part 2 Simon Horman
2013-03-28 8:57 ` Julian Anastasov
2013-03-28 9:05 ` Simon Horman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1363945614-11752-2-git-send-email-ja@ssi.bg \
--to=ja@ssi.bg \
--cc=horms@verge.net.au \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).