From: Robert Love <rml@tech9.net>
To: Andrew Morton <akpm@zip.com.au>
Cc: Pete Zaitcev <zaitcev@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] low-latency zap_page_range
Date: 22 Jul 2002 10:19:18 -0700 [thread overview]
Message-ID: <1027358358.932.8.camel@sinai> (raw)
In-Reply-To: <3D3B960C.C56D4FE2@zip.com.au>
On Sun, 2002-07-21 at 22:20, Andrew Morton wrote:
> There are actually quite a few places in the ll patch which don't
> pass ZPR_COND_RESCHED into zap_page_range. Places which are
> themselves called under locks, places where not enough pages
> are being zapped to make it necessary, etc. vmtruncate_list,
> some mremap code, others.
The bonus of the approach in my patch is that we won't reschedule unless
the lock count is zero (due to the preemptive kernel), so we do not need
to worry about the above. The only concern would be if there is ever a
case where the critical region is the entire chunk we want to zap (e.g.
we must zap the entire inputted range atomically) but I do not see that
ever being the case.
Robert Love
next prev parent reply other threads:[~2002-07-22 17:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1027196701.28591.linux-kernel2news@redhat.com>
2002-07-21 2:47 ` [PATCH] low-latency zap_page_range Pete Zaitcev
2002-07-22 5:20 ` Andrew Morton
2002-07-22 17:19 ` Robert Love [this message]
2002-07-20 20:20 Robert Love
2002-07-22 5:14 ` Andrew Morton
2002-07-22 17:58 ` Robert Love
2002-07-22 18:05 ` Linus Torvalds
2002-07-22 18:22 ` Robert Love
2002-07-22 18:28 ` Robert Love
2002-07-22 18:40 ` Andrew Morton
2002-07-22 18:50 ` Robert Love
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=1027358358.932.8.camel@sinai \
--to=rml@tech9.net \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.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