From: Jarek Poplawski <jarkao2@gmail.com>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: Badalian Vyacheslav <slavon@bigtelecom.ru>,
Patrick McHardy <kaber@trash.net>, jamal <hadi@cyberus.ca>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH 2/3][NET] gen_estimator: list_empty() check in est_timer() fixed
Date: Mon, 21 Jan 2008 07:34:55 +0100 [thread overview]
Message-ID: <20080121063455.GA981@ff.dom.local> (raw)
In-Reply-To: <20080120155544.0a071675@deepthought>
On Sun, Jan 20, 2008 at 03:55:44PM -0800, Stephen Hemminger wrote:
> On Mon, 21 Jan 2008 00:49:59 +0100
> Jarek Poplawski <jarkao2@gmail.com> wrote:
>
> > This patch changes the method of checking for empty list in est_timer():
> > list_empty() is not recommended for RCU protected lists. Now, it's simply
> > a variable used for this.
> >
> > Signed-off-by: Jarek Poplawski <jarkao2@gmail.com>
> >
> > ---
> >
> > diff -Nurp 2.6.24-rc8-mm1-p1-/net/core/gen_estimator.c 2.6.24-rc8-mm1-p1+/net/core/gen_estimator.c
> > --- 2.6.24-rc8-mm1-p1-/net/core/gen_estimator.c 2008-01-20 20:58:35.000000000 +0100
> > +++ 2.6.24-rc8-mm1-p1+/net/core/gen_estimator.c 2008-01-20 21:07:42.000000000 +0100
> > @@ -106,6 +106,7 @@ static void est_timer(unsigned long arg)
> > {
> > int idx = (int)arg;
> > struct gen_estimator *e;
> > + int list_not_empty = 0;
>
> Using a negative name for what is a boolean value leads
> to code that reads like a double negative sentence. Better to choose
> a variable name that is direct, can't use list_empty because that
> is a macro, so how about "estimator_found".
>
Hmm, seems right, but since just after sending this patch I started
to doubt this 2/3 patch could really matter here, I'll maybe wait with
this name change for some confirmation yet.
So, since it certainly doesn't matter for 1/3 and 3/3 I withdraw this
2/3 patch for now.
BTW, I've forgotten to mention with patch 1/3 that this checking with
warning on gen_new_estimator() double call should be only temporary,
and after more testing gen_estimator structure could be probably
decreased after removing bstats and rate_est fields.
Thanks,
Jarek P.
next prev parent reply other threads:[~2008-01-21 6:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-20 23:49 [PATCH 2/3][NET] gen_estimator: list_empty() check in est_timer() fixed Jarek Poplawski
2008-01-20 23:55 ` Stephen Hemminger
2008-01-21 6:34 ` Jarek Poplawski [this message]
2008-01-21 6:42 ` Jarek Poplawski
2008-01-21 10:36 ` David Miller
2008-01-21 11:19 ` Jarek Poplawski
2008-01-21 11:15 ` David Miller
2008-01-21 11:28 ` Jarek Poplawski
2008-01-21 14:43 ` Jarek Poplawski
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=20080121063455.GA981@ff.dom.local \
--to=jarkao2@gmail.com \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=slavon@bigtelecom.ru \
/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).