public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-kernel@vger.kernel.org, davem@redhat.com
Subject: Re: Should VLANs be devices or something else?
Date: 20 Jun 2001 10:26:15 +0200	[thread overview]
Message-ID: <oup3d8vftg8.fsf@pigdrop.muc.suse.de> (raw)
In-Reply-To: <3B2FCE0C.67715139@candelatech.com.suse.lists.linux.kernel> <Pine.LNX.4.33.0106191641150.17061-100000@duely.gurulabs.com.suse.lists.linux.kernel> <15151.55017.371775.585016@pizda.ninka.net.suse.lists.linux.kernel> <3B2FDD62.EFC6AEB1@candelatech.com.suse.lists.linux.kernel>
In-Reply-To: Ben Greear's message of "20 Jun 2001 01:26:03 +0200"

Ben Greear <greearb@candelatech.com> writes:
> 
> Adding the hashed lookup for devices took the exponential curve out of
> ip and ifconfig's performance, btw.

And fixing the ifconfig user data structures took it also.
Probably just ip needs similar tuning.
No need to add the name lookup hash table to the kernel.

Perhaps it would be best if you could post your current patch without
these hash tables, so that it can be properly reviewed and hopefully
merged then.

-Andi

       reply	other threads:[~2001-06-20  8:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3B2FCE0C.67715139@candelatech.com.suse.lists.linux.kernel>
     [not found] ` <Pine.LNX.4.33.0106191641150.17061-100000@duely.gurulabs.com.suse.lists.linux.kernel>
     [not found]   ` <15151.55017.371775.585016@pizda.ninka.net.suse.lists.linux.kernel>
     [not found]     ` <3B2FDD62.EFC6AEB1@candelatech.com.suse.lists.linux.kernel>
2001-06-20  8:26       ` Andi Kleen [this message]
2001-06-20 14:59         ` Should VLANs be devices or something else? Ben Greear
2001-06-19  8:19 VLAN in kernel? Holger Kiehl
2001-06-19 22:11 ` Should VLANs be devices or something else? Ben Greear
2001-06-19 22:45   ` Dax Kelson
2001-06-19 22:49     ` David S. Miller
2001-06-19 22:52       ` Dax Kelson
2001-06-19 23:16       ` Ben Greear
2001-06-20  0:31         ` Marcell Gal
2001-06-20  9:32       ` Gleb Natapov

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=oup3d8vftg8.fsf@pigdrop.muc.suse.de \
    --to=ak@suse.de \
    --cc=davem@redhat.com \
    --cc=greearb@candelatech.com \
    --cc=linux-kernel@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