All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: [PATCH] get rid of read/write lock in gen_estimator
Date: Mon, 28 Sep 2009 11:38:55 -0700	[thread overview]
Message-ID: <20090928113855.52eab44b@nehalam> (raw)

Don't need a read/write lock here sinc there already is a spin lock that
is being acquired.

Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>

--- a/net/core/gen_estimator.c	2009-09-24 16:27:01.239755070 -0700
+++ b/net/core/gen_estimator.c	2009-09-24 16:41:09.290751273 -0700
@@ -101,9 +101,6 @@ struct gen_estimator_head
 
 static struct gen_estimator_head elist[EST_MAX_INTERVAL+1];
 
-/* Protects against NULL dereference */
-static DEFINE_RWLOCK(est_lock);
-
 /* Protects against soft lockup during large deletion */
 static struct rb_root est_root = RB_ROOT;
 
@@ -118,9 +115,8 @@ static void est_timer(unsigned long arg)
 		u64 brate;
 		u32 npackets;
 		u32 rate;
-
+
 		spin_lock(e->stats_lock);
-		read_lock(&est_lock);
 		if (e->bstats == NULL)
 			goto skip;
 
@@ -136,7 +132,6 @@ static void est_timer(unsigned long arg)
 		e->avpps += (rate >> e->ewma_log) - (e->avpps >> e->ewma_log);
 		e->rate_est->pps = (e->avpps+0x1FF)>>10;
 skip:
-		read_unlock(&est_lock);
 		spin_unlock(e->stats_lock);
 	}
 
@@ -270,9 +265,9 @@ void gen_kill_estimator(struct gnet_stat
 	while ((e = gen_find_node(bstats, rate_est))) {
 		rb_erase(&e->node, &est_root);
 
-		write_lock_bh(&est_lock);
+		spin_lock(e->stats_lock);
 		e->bstats = NULL;
-		write_unlock_bh(&est_lock);
+		spin_unlock(e->stats_lock);
 
 		list_del_rcu(&e->list);
 		call_rcu(&e->e_rcu, __gen_kill_estimator);

             reply	other threads:[~2009-09-28 18:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-28 18:38 Stephen Hemminger [this message]
2009-09-28 18:50 ` [PATCH] get rid of read/write lock in gen_estimator Eric Dumazet
2009-09-28 19:42   ` David Miller

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=20090928113855.52eab44b@nehalam \
    --to=shemminger@vyatta.com \
    --cc=davem@davemloft.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.