linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Bill Mair <bill.mair@web.de>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Re: Daemon or Thread with 5 minute interval
Date: Thu, 26 May 2005 21:42:08 +0200	[thread overview]
Message-ID: <d751l5$u0e$1@sea.gmane.org> (raw)
In-Reply-To: <429606D1.7040106@hp.com>

Howard Rifkin wrote:
> 
> We do have the right kernel support for our didsks. But, you do not need 
> a lot of CPU activity to generate noise. Just enough to disrupt the 
> cashe. Does kupdated run every 5 minutes? If so it could still be the 
> culprit.

kupdated - journal update
kswapd - swapper
bdflush - flush IO

All/any of them could cause problems fir what you are doing, but I don't think
LVM is your problem.

--
Bill

  reply	other threads:[~2005-05-26 18:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-26 11:50 [linux-lvm] Daemon or Thread with 5 minute interval Howard Rifkin
2005-05-26 12:22 ` johnpaul
2005-05-26 14:48 ` [linux-lvm] " Bill Mair
2005-05-26 17:26   ` Howard Rifkin
2005-05-26 19:42     ` Bill Mair [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-26 19:29 bill.mair

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='d751l5$u0e$1@sea.gmane.org' \
    --to=bill.mair@web.de \
    --cc=linux-lvm@redhat.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).