public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Boszormenyi Zoltan <zboszor@pr.hu>
To: lkml <linux-kernel@vger.kernel.org>
Subject: loadavg question
Date: Thu, 28 Feb 2013 13:01:26 +0100	[thread overview]
Message-ID: <512F4716.4050802@pr.hu> (raw)

Hi,

on an embedded PC (500MHz AMD Geode), we recently tried
to upgrade the kernel. The original version was 2.6.27, the new
ones were 3.3.x and 3.7.x. With the same userspace (a GTK based
GUI constantly querying daemons handling different pieces of
hardware over serial ports), we noticed that loadavg is different
while the idle time (95-97%) is the same. On 2.6.27, the load was
around 0.05-0.3 while on 3.3.x and 3.7.x, it quickly crawled up
to around 5. Has the load calculation changed so dramatically
after 2.6.27?

Thanks in advance,
Zoltán Böszörményi


             reply	other threads:[~2013-02-28 12:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28 12:01 Boszormenyi Zoltan [this message]
     [not found] ` <CAAW1UO8b5gc5fD++XTvE8y1yF6N-j7LoiGnQZFzgo-3robe+zQ@mail.gmail.com>
2013-02-28 17:28   ` loadavg question Boszormenyi Zoltan

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=512F4716.4050802@pr.hu \
    --to=zboszor@pr.hu \
    --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