From: chuck gelm <chuck@gelm.net>
To: Thushara Wijeratna <thushw@gmail.com>
Cc: linux-admin@vger.kernel.org
Subject: Re: top command is a top resource hog?
Date: Tue, 11 Jul 2006 18:24:57 -0400 [thread overview]
Message-ID: <44B42539.1060402@gelm.net> (raw)
In-Reply-To: <2625b9520607111410s777921a0mb2b9293b81098add@mail.gmail.com>
Thushara Wijeratna wrote:
> I couldn't find the archive for this list. Can someone please point me
> to it?
> I'm investigating a perf issue on an AMD 8080 dualcore (8 CPU) box and
> when I run top(3.2.3), often top seems to be using 30-50% CPU. Is this
> a known issue?
>
> Thanks,
> Thushara
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Q1:
Google'd - linux admin vger archive
http://vger.kernel.org/vger-lists.html#linux-admin
Q2:
I do not know. I have top v3.2.5
HTH, Chuck
prev parent reply other threads:[~2006-07-11 22:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 21:10 top command is a top resource hog? Thushara Wijeratna
2006-07-11 22:24 ` chuck gelm [this message]
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=44B42539.1060402@gelm.net \
--to=chuck@gelm.net \
--cc=linux-admin@vger.kernel.org \
--cc=thushw@gmail.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).