From: "David Schwartz" <davids@webmaster.com>
To: <tonyosborne_a@hotmail.com>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: RE: Main CPU- I/O CPU interaction
Date: Mon, 3 Jan 2005 13:49:05 -0800 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKMEEBANAB.davids@webmaster.com> (raw)
In-Reply-To: <BAY14-F244E614A1607C5B42C47F595900@phx.gbl>
> sorry for not being clear. i meant no other application running
> while saving
> the data, i.e. CPU idle?
I still have no idea what you're talking about and I don't think anyone
else does either. For example, by CPU being idle, do you mean that it's
doing nothing? If so, how did you establish this? Are you talking about the
output of 'top', for example?
You are going to have to be precise about what your observing. You are
stating your observations in the form of conclusions, and this makes it
impossible for us to tell what you're talking about. It could be that your
misconceptions are coloring your conclusions and others would reach
different conclusions from those same observations.
Example: You are asking, "why does cutting off a frog's legs make it deaf"?
We have no idea what you're talking about. Then you explain your
*observations* which are that if you cut off all of a frog's legs, it no
longer jumps when you yell at it. We then understand that you drew the wrong
conclusion from your observation. But from just the conclusion, there's no
way to tell what you actually are seeing.
"CPU idle" is a conclusion. Something made you think your CPU was idle.
What? Same with your entire post.
DS
next prev parent reply other threads:[~2005-01-03 21:52 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 [this message]
2005-01-03 22:27 ` Valdis.Kletnieks
2005-01-04 22:03 ` Alan Cox
2005-01-05 6:53 ` Tom Felker
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=MDEHLPKNGKAHNMBLJOLKMEEBANAB.davids@webmaster.com \
--to=davids@webmaster.com \
--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®