From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Kenny Simpson <theonetruekenny@gmail.com>
Cc: Michal Hocko <mhocko@suse.cz>,
linux-kernel@vger.kernel.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Dave Jones <davej@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Armin Rigo <arigo@tunes.org>
Subject: Re: remap_file_pages() use
Date: Mon, 19 May 2014 17:35:40 +0300 (EEST) [thread overview]
Message-ID: <20140519143540.BE9F6E009B@blue.fi.intel.com> (raw)
In-Reply-To: <20140519130114.GA3140@dhcp22.suse.cz>
Michal Hocko wrote:
> [CCing Kirill and other people involved]
>
> On Sun 18-05-14 00:03:28, Kenny Simpson wrote:
> > I saw that remap_file_pages() was possibly going away to be replaced
> > by some emulation. I've used this call in several projects over the
> > years mostly as a way of mapping multiple virtual memory pages to
> > alias the same private or shared memory region (to do things like
> > circular buffers). mmap()
> > in the case of anonymous memory doesn't work as well since there is
> > not a file descriptor to reference.
> >
> > Would this sort of thing be supported in the emulation, or should I be
> > planning on reimplementing/rewriting some things?
>From functional POV, emulation *should* be identical to original
remap_file_pages(), but slower. It would be nice, if you test it early.
It's not clear yet how long emulation will be there.
Is there a reason why you can't use fd from shared memory (shm_open() or
direct open() on /dev/shm/xxx)?
--
Kirill A. Shutemov
next prev parent reply other threads:[~2014-05-19 14:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-18 4:03 Kenny Simpson
2014-05-19 13:01 ` Michal Hocko
2014-05-19 14:35 ` Kirill A. Shutemov [this message]
2014-05-19 14:38 ` Christoph Hellwig
2014-05-19 15:02 ` Kirill A. Shutemov
2014-05-19 15:11 ` Christoph Hellwig
2014-05-19 15:17 ` Kirill A. Shutemov
2014-05-19 15:42 ` Armin Rigo
2014-05-19 15:53 ` Kirill A. Shutemov
2014-05-19 16:42 ` Armin Rigo
2014-05-19 17:50 ` Dave Hansen
2014-05-19 22:05 ` Armin Rigo
2014-05-19 16:56 ` Christoph Hellwig
2014-05-19 19:14 ` Richard Weinberger
2014-05-26 0:19 ` Jeff Smith
2014-05-26 9:42 ` Kirill A. Shutemov
2014-05-26 13:24 ` Jeff Smith
2014-05-26 13:35 ` Paolo Bonzini
2014-05-26 13:38 ` Jeff Smith
2014-05-26 13:47 ` Kirill A. Shutemov
2014-05-26 13:52 ` Jeff Smith
2014-05-26 14:16 ` Kirill A. Shutemov
2014-05-26 13:37 ` Kirill A. Shutemov
2014-05-19 17:34 ` Kenny Simpson
2014-05-19 21:24 ` Kirill A. Shutemov
2014-05-21 1:53 ` Kenny Simpson
2014-05-21 3:56 ` Kenny Simpson
2014-05-21 4:32 ` Hugh Dickins
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=20140519143540.BE9F6E009B@blue.fi.intel.com \
--to=kirill.shutemov@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=arigo@tunes.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=peterz@infradead.org \
--cc=theonetruekenny@gmail.com \
--cc=torvalds@linux-foundation.org \
/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
Powered by JetHome