public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] vmap: add flag to allow lazy unmap to be disabled at runtime
Date: Tue, 27 Jul 2010 14:13:49 -0400	[thread overview]
Message-ID: <20100727181349.GA15674@phenom.dumpdata.com> (raw)
In-Reply-To: <20100727082439.GB6332@amd>

On Tue, Jul 27, 2010 at 06:24:39PM +1000, Nick Piggin wrote:
> On Mon, Jul 26, 2010 at 01:24:51PM -0700, Jeremy Fitzhardinge wrote:
> > 
> > 
> > [ Nick, I forget if I sent this to you before.  Could you Ack it if it looks OK? Thanks, J ]
> > 
> > Add a flag to force lazy_max_pages() to zero to prevent any outstanding
> > mapped pages.  We'll need this for Xen.
> 
> You have sent this to me before, probably several times, and I always
> forget about it right as you send it again.
> 
> It's no problem merging something like this for Xen, although as you
> know I would love to see an approach where Xen would benefit from
> delayed flushing as well :)

Hey Nick,

So I've posted the patch with your Ack, in this thread
http://lkml.org/lkml/2010/7/27/246. I hope that is OK?

I think that using the delayed flushing is appropiate long-term.
I don't know that much about it but I will put it on the list of todo.
Fortunatly that list is actually shrinking (amazing!).

  reply	other threads:[~2010-07-27 18:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 20:24 [PATCH] vmap: add flag to allow lazy unmap to be disabled at runtime Jeremy Fitzhardinge
2010-07-27  8:24 ` Nick Piggin
2010-07-27 18:13   ` Konrad Rzeszutek Wilk [this message]
2010-07-27 18:56   ` Jeremy Fitzhardinge

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=20100727181349.GA15674@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    /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