netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: Krishna Kumar <krkumar2@in.ibm.com>
Cc: kaber@trash.net, netdev@vger.kernel.org, davem@davemloft.net,
	herbert@gondor.apana.org.au
Subject: Re: [PATCH] Speed-up pfifo_fast lookup using a bitmap
Date: Fri, 14 Aug 2009 23:36:43 +0200	[thread overview]
Message-ID: <20090814213643.GA3179@ami.dom.local> (raw)
In-Reply-To: <20090814132458.27518.65144.sendpatchset@localhost.localdomain>

On Fri, Aug 14, 2009 at 06:54:58PM +0530, Krishna Kumar wrote:
> ďťżHi Jarek,
> 
> Jarek Poplawski <jarkao2@gmail.com> wrote on 08/14/2009 04:31:27 PM:
> 
> > Alas, private or public, these values are lower on average than
> > before, so I'm not sure the complexity (especially in reading) added
> > by this patch is worth it. So, I can only say it looks formally OK,
> > except the changelog and maybe 2 cosmetical suggestions below.
> 
> Maybe the different test parameters result in smaller improvements.
> I agree with you - the first approach is very readable and probably
> preferable, while the second introduces a new structure and more
> complexity.

Actually, I meant the complexity added by any of these versions. If
you declare: "This helps in faster lookup for a skb when there are no
high priority skbs.", there is a question if less than 1% is enough.

> I am sending both these versions a last time, after fixing your
> comments in case someone can help decide if one or the other is
> better (sorry I forgot to run checkpatch couple of times, will try
> to remember next time).

I definitely can't see a reason to make this variable public, and
prefer the private (v2) version (which still lacks a changelog, btw).

Thanks,
Jarek P.

  parent reply	other threads:[~2009-08-14 21:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-14 13:24 [PATCH] Speed-up pfifo_fast lookup using a bitmap Krishna Kumar
2009-08-14 13:25 ` [PATCH v1] Speed-up pfifo_fast lookup using a public bitmap Krishna Kumar
2009-08-14 13:25 ` [PATCH v2] Speed-up pfifo_fast lookup using a private bitmap Krishna Kumar
2009-08-14 21:36 ` Jarek Poplawski [this message]
2009-08-18  2:03   ` [PATCH] Speed-up pfifo_fast lookup using a bitmap David Miller
2009-08-18 16:46     ` Krishna Kumar2
  -- strict thread matches above, loose matches on Subject: below --
2009-08-14  8:19 Krishna Kumar
2009-08-14 11:01 ` Jarek Poplawski
2009-08-13  7:28 Krishna Kumar
2009-08-13 10:08 ` Jarek Poplawski
2009-08-13 10:41   ` Krishna Kumar2
2009-08-13 11:27     ` 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=20090814213643.GA3179@ami.dom.local \
    --to=jarkao2@gmail.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=kaber@trash.net \
    --cc=krkumar2@in.ibm.com \
    --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).