From: Andrew Morton <akpm@zip.com.au>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: alad@hss.hns.com, linux-kernel@vger.kernel.org
Subject: Re: locked page handling
Date: Mon, 31 Dec 2001 12:23:45 -0800 [thread overview]
Message-ID: <3C30C951.DC96E2B6@zip.com.au> (raw)
In-Reply-To: <65256B33.0039476C.00@sandesh.hss.hns.com> <3C30BE70.6E5E95CE@zip.com.au>, <3C30BE70.6E5E95CE@zip.com.au> <E16L8aA-0000at-00@starship.berlin>
Daniel Phillips wrote:
>
> I think we want the pages in process of being written to live on a separate
> list. Pages can be pulled of that list by a separate thread, or perhaps in
> the IO completion interrupt (opportunistically, if the list lock is available)
> meaning kswapd would block less and waste less time examining locked pages.
Yes, possibly. Also the unlocked pages which have locked buffers,
which tends to be 99% of the pages...
But then again:
- I've never seen this code disgrace itself in profiler output unless
it's in already-hopelessly-confused mode.
- Personally, I wouldn't recommend anything like that without having
previously done a deep analysis of the existing implementation's
dynamics and behaviour. Something which would take a week (or two,
given the way the elevator analysis is shaping up).
This activity is something which I have never countenanced because
the code has been under continual futzing for a year.
-
next prev parent reply other threads:[~2001-12-31 20:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-31 10:20 locked page handling alad
2001-12-31 19:37 ` Andrew Morton
2001-12-31 19:49 ` Andrew Morton
2001-12-31 19:58 ` Daniel Phillips
2001-12-31 20:23 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-02 4:58 alad
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=3C30C951.DC96E2B6@zip.com.au \
--to=akpm@zip.com.au \
--cc=alad@hss.hns.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.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 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.