All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason C. Leach" <jleach@ocis.net>
To: linux-raid@vger.kernel.org
Subject: I/O Blocking
Date: Thu, 22 Jul 2004 09:29:09 -0700	[thread overview]
Message-ID: <40FFEB55.2000905@ocis.net> (raw)

Hi,

Both the RAID (Promise SuperTrak 6000) or the USB subsystems really 
drive the system load up. I'm using a AMD 3200+ system that is only a 
few months old with the 2.4.25 kernel.  When the I/O systems are 
blocking the system is very unresponsive. Some times samba will timeout, 
or I'll wait several seconds for commands like df, top, w and so on.

I am wondering if I were to use a dual CPU system, would this solve my 
I/O blocking problem?  Would one CPU tend to the I/O subsystem and the 
second would deal with other system requests I (samba, DB, LDAP, ...)?

             reply	other threads:[~2004-07-22 16:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-22 16:29 Jason C. Leach [this message]
2004-07-22 18:02 ` I/O Blocking Guy
2004-07-22 18:09   ` Jason C. Leach
2004-07-22 18:37     ` Guy
2004-07-22 19:51 ` Kanoa Withington
2004-07-23  1:47 ` berk walker

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=40FFEB55.2000905@ocis.net \
    --to=jleach@ocis.net \
    --cc=linux-raid@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.