From: Boszormenyi Zoltan <zboszor@pr.hu>
To: Azat Khuzhin <dohardgopro@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: loadavg question
Date: Thu, 28 Feb 2013 18:28:34 +0100 [thread overview]
Message-ID: <512F93C2.7050105@pr.hu> (raw)
In-Reply-To: <CAAW1UO8b5gc5fD++XTvE8y1yF6N-j7LoiGnQZFzgo-3robe+zQ@mail.gmail.com>
Hi,
yes, that commit is in my kernel 3.7.9 kernel source, but not in 3.3.2.
Also, I have CONFIG_NO_HZ=n in my .config. I will retry with
CONFIG_NO_HZ=y with 3.7.9.
Thanks,
Zoltán Böszörményi
2013-02-28 15:05 keltezĂŠssel, Azat Khuzhin Ărta:
>
> Hi,
>
> Could you check do you have commit that mentioned here?
> http://comments.gmane.org/gmane.linux.kernel/1346108
>
> Respectfully
> Azat Khuzhin.
> >From phone.
>
> On Feb 28, 2013 4:40 PM, "Boszormenyi Zoltan" <zboszor@pr.hu <mailto:zboszor@pr.hu>> wrote:
>
> 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
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org <mailto:majordomo@vger.kernel.org>
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
prev parent reply other threads:[~2013-02-28 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 12:01 loadavg question Boszormenyi Zoltan
[not found] ` <CAAW1UO8b5gc5fD++XTvE8y1yF6N-j7LoiGnQZFzgo-3robe+zQ@mail.gmail.com>
2013-02-28 17:28 ` Boszormenyi Zoltan [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=512F93C2.7050105@pr.hu \
--to=zboszor@pr.hu \
--cc=dohardgopro@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.