From: David Miller <davem@davemloft.net>
To: sphink@gmail.com
Cc: netdev@vger.kernel.org, stephen.hemminger@vyatta.com
Subject: Re: ss -p is much too slow
Date: Fri, 23 Jul 2010 12:48:19 -0700 (PDT) [thread overview]
Message-ID: <20100723.124819.246519789.davem@davemloft.net> (raw)
In-Reply-To: <20100628.162139.59679342.davem@davemloft.net>
From: David Miller <davem@davemloft.net>
Date: Mon, 28 Jun 2010 16:21:39 -0700 (PDT)
> ss: Avoid quadradic complexity with '-p'
>
> Scan the process list of open sockets once, and store in a hash
> table to be used by subsequent find_user() calls.
>
> Reported-by: Steve Fink <sphink@gmail.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
Stephen, please apply this, it fixes the quadratic behavior and
has been sitting for a month.
It's in patchwork, just check your todo list.
Thanks.
next prev parent reply other threads:[~2010-07-23 19:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 18:42 ss -p is much too slow Steve Fink
2010-06-28 23:21 ` David Miller
2010-07-23 19:48 ` David Miller [this message]
2010-07-23 20:01 ` Stephen Hemminger
2010-08-01 2:33 ` Stephen Hemminger
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=20100723.124819.246519789.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sphink@gmail.com \
--cc=stephen.hemminger@vyatta.com \
/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).