From: Zach Brown <zab@zabbo.net>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: Dmitry Monakhov <dmonakhov@gmail.com>,
Pavel Emelyanov <xemul@parallels.com>,
Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>,
linux-aio@kvack.org, Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH] aio: Make it possible to remap aio ring
Date: Thu, 25 Sep 2014 11:12:26 -0700 [thread overview]
Message-ID: <20140925181226.GM920@lenny.home.zabbo.net> (raw)
In-Reply-To: <20140925151316.GO8303@kvack.org>
> > > To make restore possible I'm going to mremap() the freshly created ring
> > > into the address A (under which it was seen before dump).
> > > What do you think?
> > Look reasonable.
> > Feel free to add Acked-by:Dmitry Monakhov <dmonakhov@openvz.org>
> > >
> > > Signed-off-by: Pavel Emelyanov <xemul@parallels.com>
>
> I've had a look over this patch, and it seems okay to me. The interaction
> with page migration looks safe, as well as with io_destroy(). I've applied
> this to my aio-next tree at git://git.kvack.org/~bcrl/aio-next.git . If
> mm folks have any concerns, please let me know.
I can chime in with generic support: the C/R folks have complained about
the implicit context mapping in the past. I'm all for letting them
explicitly re-establish it, though I didn't actually look at the patch.
- z
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2014-09-25 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 15:56 Pavel Emelyanov
2014-09-25 12:18 ` Dmitry Monakhov
2014-09-25 15:13 ` Benjamin LaHaise
2014-09-25 18:12 ` Zach Brown [this message]
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=20140925181226.GM920@lenny.home.zabbo.net \
--to=zab@zabbo.net \
--cc=akpm@linux-foundation.org \
--cc=bcrl@kvack.org \
--cc=dmonakhov@gmail.com \
--cc=hughd@google.com \
--cc=linux-aio@kvack.org \
--cc=linux-mm@kvack.org \
--cc=xemul@parallels.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