netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Michal Vanco <vanco@satro.sk>
Cc: netdev@oss.sgi.com
Subject: Re: 2.6.11 on AMD64 traps
Date: Wed, 09 Mar 2005 22:05:27 +0100	[thread overview]
Message-ID: <422F6517.6070301@trash.net> (raw)
In-Reply-To: <200503092142.50027.vanco@satro.sk>

Michal Vanco wrote:
> On Wednesday 09 March 2005 21:34, Patrick McHardy wrote:
>>
>>Yes, I know it is totally inefficient. Just use ip route, which doesn't
>>suffer from this problem.
> 
> Sure. Can (or will) this ever be fixed to any usable state also with netstat?
> Is this problem related only to AMD64?

Maybe. To start dumping entries of an open hashed hash-table at a
specific position we need to skip all entries before that position by
walking over them. This results in quadratic time complexity. It might
be possible to improve this by cacheing the last position in
fib_iter_state even between ->stop() and ->start() calls and using
generation IDs for invalidation.

Regards
Patrick

  reply	other threads:[~2005-03-09 21:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200503081900.18686.vanco@satro.sk>
2005-03-08 18:35 ` 2.6.11 on AMD64 traps Andre Tomt
2005-03-09 19:45   ` Patrick McHardy
2005-03-09 20:24     ` Michal Vanco
2005-03-09 20:34       ` Patrick McHardy
2005-03-09 20:42         ` Michal Vanco
2005-03-09 21:05           ` Patrick McHardy [this message]
2005-03-09 21:17             ` Michal Vanco
2005-03-09 23:27               ` Patrick McHardy
2005-03-09 23:50                 ` Michal Vanco
2005-03-09 23:57                   ` Patrick McHardy
2005-03-10  0:43                     ` David S. Miller
2005-03-11  2:20     ` David S. 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=422F6517.6070301@trash.net \
    --to=kaber@trash.net \
    --cc=netdev@oss.sgi.com \
    --cc=vanco@satro.sk \
    /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).