From: Tom Felker <tfelker2@uiuc.edu>
To: "tony osborne" <tonyosborne_a@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Main CPU- I/O CPU interaction
Date: Wed, 5 Jan 2005 00:53:13 -0600 [thread overview]
Message-ID: <200501050053.13744.tfelker2@uiuc.edu> (raw)
In-Reply-To: <BAY14-F83B94FD7D13C5D19883F795900@phx.gbl>
On Sunday 02 January 2005 06:44 pm, tony osborne wrote:
> Hello,
>
> I wish to be personally CC'ed the answers/comments posted to the list in
> response to this post .
>
>
> The I/O devices are equipped with dedicated processor to free the main CPU
> from doing the low level I/O operations. However, if i am editing and
> updating a big size file and i want to save
> it afterwards, i notice my PC getting blocked while saving the file which
> theoritically should NOT happen as it is up to the I/O device processor and
> not the main CPU to save the data into the disk; the main CPU could switch
> to another process after giving the high level command -save-to the device
> processor; so why the main CPU is blocked while saving such big size files
>
> thanks
Check to make sure DMA is on:
hdparm /dev/hda
If not, try turning it on:
hdparm -d 1 /dev/hda
When it's not on, you'll get bad performance (I usually get around 2 MB/s
according to "hdparm -t /dev/hda") and high system CPU usage. Because the
rate is so low, for big files, the high CPU usage starves other processes for
long enough that you notice. With DMA, the transfer will be much faster and
the CPU usage will be minimal.
--
Tom Felker, <tcfelker@mtco.com>
<http://vlevel.sourceforge.net> - Stop fiddling with the volume knob.
If nature has made any one thing less susceptible than all others of exclusive
property, it is the action of the thinking power called an idea.
prev parent reply other threads:[~2005-01-05 6:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-03 0:44 tony osborne
2005-01-03 16:12 ` Martin Waitz
2005-01-03 18:51 ` David Schwartz
2005-01-03 21:03 ` tony osborne
2005-01-03 21:49 ` David Schwartz
2005-01-03 22:27 ` Valdis.Kletnieks
2005-01-04 22:03 ` Alan Cox
2005-01-05 6:53 ` Tom Felker [this message]
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=200501050053.13744.tfelker2@uiuc.edu \
--to=tfelker2@uiuc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=tonyosborne_a@hotmail.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
all inboxes | Powered by JetHome®