mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: "HOLTZ, CORBIN L. (JSC-ER) (LM)" <corbin.l.holtz1@jsc.nasa.gov>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Disable kscand/Normal?
Date: Thu, 26 Aug 2004 15:32:02 +1000	[thread overview]
Message-ID: <cone.1093498322.335520.27013.502@pc.kolivas.org> (raw)
In-Reply-To: <A850C6B3EB02F044907B475259FFF56501724A18@jsc-mail08.jsc.nasa.gov>

HOLTZ, CORBIN L. (JSC-ER) (LM) writes:

> Hello,
> 
> Sorry to post to the list without being subscribed, but I've searched the
> web for information on this and I can't find anything useful.  I'm currenty
> building a realtime visualization system for a Space Shuttle landing
> simulator at NASA.  I'm using a small network of 5 Pentium 4 computers
> running RedHat's 2.4.20-31.9 kernel.  I'm easily running 60 frames/second on
> my systems, but I'm having a problem because the kscand/Normal thread comes
> in every 25 seconds and causes me to drop a frame (very annoying).  I've
> looked into the kernel source and found where the kscand threads are
> spawned.  I also see where the 25 second period is coming from.  What I'm
> wondering is what would happen if I disabled the kscand/Normal thread?  I've
> got plenty of memory, and my process is the only thing running on the
> system.  Would I eventually see problems, or would I be OK since I'm not
> running low on memory?  What if I modified the kernel to allow me to
> temporarily disable the thread while my application is running (using a
> /proc file or something similar)?  Sorry if this is a bad question, but I
> figure the people on this list are the best source of info.
> 
> Please CC: me directly since I'm not subscribed to the list. 

That vendor kernel that you're running has the rmap vm which has the kscand 
daemon. If you build a newer vanilla kernel it will not have the kscand 
daemon. Alternatively, you can manually nice the the kscand daemon as root 
to a lower value (not sure what it is by default) say nice +19. You can also 
rebuild your vendor's kernel and edit the code to set the nice level 
on spawning the daemon (obviously this requires more knowledge than the 
previous options).

Cheers,
Con


  reply	other threads:[~2004-08-26  5:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26  3:54 HOLTZ, CORBIN L. (JSC-ER) (LM)
2004-08-26  5:32 ` Con Kolivas [this message]
2004-08-26 18:03 ` Lee Revell

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=cone.1093498322.335520.27013.502@pc.kolivas.org \
    --to=kernel@kolivas.org \
    --cc=corbin.l.holtz1@jsc.nasa.gov \
    --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

all inboxes | Powered by JetHome®