From: "Jason C. Leach" <jleach@ocis.net>
To: Guy <bugzilla@watkins-home.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: I/O Blocking
Date: Thu, 22 Jul 2004 11:09:53 -0700 [thread overview]
Message-ID: <410002F1.3050703@ocis.net> (raw)
In-Reply-To: <200407221802.i6MI2n328114@watkins-home.com>
Guy:
CPU load is very low (95-96% idle), load avg is 2. The system has 512MB
RAM, some free and only a few megs swapped out. If I was really working
the RAID card I would get load avgs more like 2.5-3. Right now just
light USB and system usage and I am at 2.
I though if one CPU was tied up with the process that is blocking (using
the RAID card), then the second would be free to deal with user
requests. Or am I misunderstanding SMP and blocking I/O?
J.
Guy wrote:
>What is the CPU load like? Are you at 100%? If so a second CPU may help.
>If you are blocked on i/o it should not use much CPU, so my guess is your
>CPU load is very low, and a second CPU won't do much. How much RAM do you
>have? Are you swapping?
>
>Guy
>
>-----Original Message-----
>From: linux-raid-owner@vger.kernel.org
>[mailto:linux-raid-owner@vger.kernel.org] On Behalf Of Jason C. Leach
>Sent: Thursday, July 22, 2004 12:29 PM
>To: linux-raid@vger.kernel.org
>Subject: I/O Blocking
>
>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, ...)?
>-
>To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
next prev parent reply other threads:[~2004-07-22 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 16:29 I/O Blocking Jason C. Leach
2004-07-22 18:02 ` Guy
2004-07-22 18:09 ` Jason C. Leach [this message]
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=410002F1.3050703@ocis.net \
--to=jleach@ocis.net \
--cc=bugzilla@watkins-home.com \
--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.