public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: Robert Love <rml@tech9.net>, akpm@zip.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] low-latency zap_page_range
Date: Sat, 20 Jul 2002 22:47:33 -0400	[thread overview]
Message-ID: <200207210247.g6L2lXE13782@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1027196701.28591.linux-kernel2news@redhat.com>

> The lock hold time in zap_page_range is horrid.  This patch breaks the
> work up into chunks and relinquishes the lock after each iteration. 
> This drastically lowers latency by creating a preemption point, as well
> as lowering lock contention. 

>  void zap_page_range(struct vm_area_struct *vma, unsigned long address, unsigned long size)

Arjan sent me something similar, done by AKPM, only he did this a
little differently. He added an argument to zap_page_range
which allowed to work it in the old way, if set. Then, he set it so
all places would use low latency EXCEPT a reading from /dev/zero.
I assume it was some locking somewhere in devices/char/mem.c,
though I was unable to figure which in particular.

Andrew, care to unconfuse me?

-- Pete

       reply	other threads:[~2002-07-21  2:44 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 ` Pete Zaitcev [this message]
2002-07-22  5:20   ` [PATCH] low-latency zap_page_range Andrew Morton
2002-07-22 17:19     ` Robert Love
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=200207210247.g6L2lXE13782@devserv.devel.redhat.com \
    --to=zaitcev@redhat.com \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.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