public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Klaus Ripke <klaus@ripke.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: LOAD_FREQ (4*HZ+61) avoids loadavg Moire
Date: Mon, 14 Nov 2011 09:10:44 +0100	[thread overview]
Message-ID: <4EC0CD04.4090107@ladisch.de> (raw)
In-Reply-To: <20111112143825.GX6192@aine.Speedport_W_502V_Typ_A>

Klaus Ripke wrote:
> With some seconds based load (like SSL heartbeats)
> and LOAD_FREQ at (5*HZ+1) I see Moire patterns like inverse sawtooth,

Thanks for researching this, but I don't see them because I'm too lazy
to reproduce this.  Could you please publish a colorful screenshot
somewhere?

> I suggest (4*HZ+61) for a better distribution.

It appears your attached patch got lost somehow.  ;-)


Regards,
Clemens

  reply	other threads:[~2011-11-14  8:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-12 14:38 LOAD_FREQ (4*HZ+61) avoids loadavg Moire Klaus Ripke
2011-11-14  8:10 ` Clemens Ladisch [this message]
2011-11-16 11:03   ` Klaus Ripke
2011-11-16 11:10     ` Alan Cox

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=4EC0CD04.4090107@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=klaus@ripke.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox