netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Chris Mi <chrism@mellanox.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch net-next 1/3] idr: Use unsigned long instead of int
Date: Thu, 17 Aug 2017 00:44:10 +0300	[thread overview]
Message-ID: <20170816214410.GA13430@avx2> (raw)
In-Reply-To: <1502849538-14284-2-git-send-email-chrism@mellanox.com>

	[CC trimmed]

On Tue, Aug 15, 2017 at 10:12:16PM -0400, Chris Mi wrote:
> IDR uses internally radix tree which uses unsigned long. It doesn't
> makes sense to have index as signed value.

It doesn't. But it makes sense to use "unsigned int" because it
generates smaller code on x86_64.

  reply	other threads:[~2017-08-16 21:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-16  2:12 [patch net-next 0/3] net/sched: Improve getting objects by indexes Chris Mi
     [not found] ` <1502849538-14284-1-git-send-email-chrism-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-08-16  2:12   ` [patch net-next 1/3] idr: Use unsigned long instead of int Chris Mi
2017-08-16 21:44     ` Alexey Dobriyan [this message]
2017-08-16  2:12   ` [patch net-next 2/3] net/sched: Change cls_flower to use IDR Chris Mi
2017-08-16  2:12   ` [patch net-next 3/3] net/sched: Change act_api and act_xxx modules " Chris Mi
2017-08-16  7:49   ` [patch net-next 0/3] net/sched: Improve getting objects by indexes Christian König
2017-08-16  8:16     ` Jiri Pirko
2017-08-16  8:31       ` Christian König
2017-08-16  8:39         ` Jiri Pirko
2017-08-16  8:55           ` Christian König
2017-08-16  9:31             ` Jiri Pirko
2017-08-16  9:41               ` Christian König
2017-08-16 14:28         ` David Laight
2017-08-16  9:19     ` Chris Wilson
2017-08-16  3:05 ` David Miller
2017-08-16  3:38   ` Chris Mi

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=20170816214410.GA13430@avx2 \
    --to=adobriyan@gmail.com \
    --cc=chrism@mellanox.com \
    --cc=linux-kernel@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).