kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: gmate.amit@gmail.com (Kumar amit mehta)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Direct IO and Page cache
Date: Fri, 26 Jul 2013 11:52:33 -0400	[thread overview]
Message-ID: <20130726155233.GA19265@gmail.com> (raw)
In-Reply-To: <38106.1374850765@turing-police.cc.vt.edu>

On Fri, Jul 26, 2013 at 10:59:25AM -0400, Valdis.Kletnieks at vt.edu wrote:
> On Fri, 26 Jul 2013 00:02:31 -0400, Kumar amit mehta said:
> 
> > So leaving the hardware at the mercy of the application doesn't sound
> > like a good practice. This __may__ compromise kernel stability too. Also
> > think of this:
> 
> In what possible way does it compromise kernel stability?

Sorry for forgetting that we are talking about userspace programs.
Recently I came across an old HBA driver, which for some reason failed
to properly intialize the firmware(maybe someone didn't properly copied
the firmware in the /lib/firmware directory, i don't know) and because
of that the firmware initialization code tried the same thing for a
couple of iteration, failiing which it tried to reset the board, but
somewhere during this recovery process started disabling the interrupt
on the CPU. Later, watchdog timer kicked in, considering this as hard
lock up and issued a system reset.

When I first saw the firmware initialization error, I thought what harm
this could bring to my overall system other than the particular HBA
turning into an unusable one, but It turned out to be much more disruptive.
When I said "This __may__ compromise kernel stability too", I was
thinking, something on those lines and completely forgot that we are
currently in uspace.

!!amit

  reply	other threads:[~2013-07-26 15:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26  3:15 Direct IO and Page cache Kumar amit mehta
2013-07-26  9:14 ` Chinmay V S
2013-07-26  4:02   ` Kumar amit mehta
2013-07-26 10:21     ` Chinmay V S
2013-07-26 10:31       ` Chinmay V S
2013-07-26  6:04         ` Kumar amit mehta
2013-07-26 14:59     ` Valdis.Kletnieks at vt.edu
2013-07-26 15:52       ` Kumar amit mehta [this message]
2013-07-26 14:56 ` Valdis.Kletnieks at vt.edu

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=20130726155233.GA19265@gmail.com \
    --to=gmate.amit@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).