public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Matthew Zahorik <matt@albany.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How does the disk buffer cache work?
Date: Mon, 30 Dec 2002 20:14:03 -0800	[thread overview]
Message-ID: <3E11198B.EEDE0DC0@digeo.com> (raw)
In-Reply-To: Pine.BSF.4.43.0212302153400.370-100000@ender.tmmz.net

Matthew Zahorik wrote:
> 
> On Mon, 30 Dec 2002, Andrew Morton wrote:
> 
> > > [.. the next function call in read_cache_page() is lock_page(), which we
> > > hang forever on ..]
> >
> > lock_page() will sleep until the page is unlocked.  The page is unlocked
> > from end_buffer_io_sync(), which is called from within the context of
> > the disk device driver's interrupt handler.
> 
> Okay, I'll track it down there.  Probably the driver not calling
> end_buffer_io_sync() when timed out.  When the bad drive is detached,
> things work fine - leading me to believe that hardware and interrupt
> routing wise things are okay.
> 

It won't call end_buffer_io_sync() explicitly - it calls the function which
is pointed at by the relevant buffer's b_end_io vector.  Typically that
will point at end_buffer_io_aysnc() or end_buffer_io_sync()

  reply	other threads:[~2002-12-31  4:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-31  0:33 How does the disk buffer cache work? Matthew Zahorik
2002-12-31  1:24 ` Andrew Morton
2002-12-31  2:58   ` Matthew Zahorik
2002-12-31  4:14     ` Andrew Morton [this message]
2003-01-01 19:19   ` sd driver NOT_READY behavior / was " Matthew Zahorik
2003-01-01 21:32     ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2003-01-05  1:29 John Bäckstrand
2003-01-05 19:08 John Bäckstrand
2003-01-06 10:30 John Bäckstrand

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=3E11198B.EEDE0DC0@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@albany.net \
    /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