linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Armin Rigo <arigo@tunes.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	peterz@infradead.org, mingo@kernel.org
Subject: Re: [PATCH 2/2] mm: replace remap_file_pages() syscall with emulation
Date: Tue, 13 May 2014 09:32:13 +0200	[thread overview]
Message-ID: <CAMSv6X0yg4haVtUifFrdkCCZjJV-TLXJ-KsiCPiBue0Y0qNTcQ@mail.gmail.com> (raw)
In-Reply-To: <5370E4B4.1060802@oracle.com>

Hi Sasha,

On 12 May 2014 17:11, Sasha Levin <sasha.levin@oracle.com> wrote:
> Since we can't find any actual users,

The PyPy project doesn't count as an "actual user"?  It's not just an
idea in the air.  It's beta code that is already released (and open
source):

http://morepypy.blogspot.ch/2014/04/stm-results-and-second-call-for.html

The core library is available from there (see the test suite in c7/test/):

https://bitbucket.org/pypy/stmgc

I already reacted to the discussion here by making remap_file_pages()
optional (#undef USE_REMAP_FILE_PAGES) but didn't measure the
performance impact of this, if any (I expect it to be reasonable).
Still, if you're looking for a real piece of code using
remap_file_pages(), it's one.


A bientôt,

Armin.

  parent reply	other threads:[~2014-05-13  7:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 12:41 [PATCHv2 0/2] remap_file_pages() decommission Kirill A. Shutemov
2014-05-08 12:41 ` [PATCH 1/2] mm: mark remap_file_pages() syscall as deprecated Kirill A. Shutemov
2014-06-12  5:48   ` Michael Kerrisk
2014-06-12  9:40     ` Kirill A. Shutemov
2014-06-12  9:44       ` Michael Kerrisk (man-pages)
2014-05-08 12:41 ` [PATCH 2/2] mm: replace remap_file_pages() syscall with emulation Kirill A. Shutemov
2014-05-08 21:57   ` Andrew Morton
2014-05-12 15:11     ` Sasha Levin
2014-05-12 17:05       ` Kirill A. Shutemov
2014-05-14 20:52         ` Sasha Levin
2014-05-14 21:17           ` Kirill A. Shutemov
2014-05-14 21:40             ` Andrew Morton
2014-05-13  7:32       ` Armin Rigo [this message]
2014-05-13 12:57         ` Sasha Levin
2014-05-08 15:35 ` [PATCHv2 0/2] remap_file_pages() decommission Linus Torvalds
2014-05-08 15:44 ` Armin Rigo
2014-05-08 16:02   ` Kirill A. Shutemov
2014-05-08 16:08     ` Linus Torvalds
2014-05-09 14:05       ` Kirill A. Shutemov
2014-05-09 15:14         ` Linus Torvalds
2014-05-09 18:19           ` Kirill A. Shutemov
2014-05-12 12:43           ` Kirill A. Shutemov
2014-05-12 14:59             ` Konstantin Khlebnikov
2014-05-12  3:36   ` Andi Kleen
2014-05-12  5:16     ` Konstantin Khlebnikov
2014-05-12  7:50     ` Armin Rigo

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=CAMSv6X0yg4haVtUifFrdkCCZjJV-TLXJ-KsiCPiBue0Y0qNTcQ@mail.gmail.com \
    --to=arigo@tunes.org \
    --cc=akpm@linux-foundation.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=sasha.levin@oracle.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;
as well as URLs for NNTP newsgroup(s).