From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dave Hansen <dave.hansen@intel.com>,
Andrey Ryabinin <a.ryabinin@samsung.com>,
Sasha Levin <sasha.levin@oracle.com>,
David Rientjes <rientjes@google.com>,
linux-mm@kvack.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: [PATCH 0/2] faultaround updates
Date: Tue, 29 Jul 2014 14:33:27 +0300 [thread overview]
Message-ID: <1406633609-17586-1-git-send-email-kirill.shutemov@linux.intel.com> (raw)
One fix and one tweak for faultaround code.
As alternative, we could just drop debugfs interface and make
fault_around_bytes constant.
Kirill A. Shutemov (2):
mm: close race between do_fault_around() and fault_around_bytes_set()
mm: mark fault_around_bytes __read_mostly
mm/memory.c | 20 +++++++++++++-------
1 file changed, 13 insertions(+), 7 deletions(-)
--
2.0.1
--
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>
next reply other threads:[~2014-07-29 11:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 11:33 Kirill A. Shutemov [this message]
2014-07-29 11:33 ` [PATCH 1/2] mm: close race between do_fault_around() and fault_around_bytes_set() Kirill A. Shutemov
2014-07-29 13:32 ` Andrey Ryabinin
2014-07-29 14:27 ` Kirill A. Shutemov
2014-07-29 17:07 ` Andrey Ryabinin
2014-07-29 22:36 ` David Rientjes
2014-07-29 23:16 ` Kirill A. Shutemov
2014-07-29 11:33 ` [PATCH 2/2] mm: mark fault_around_bytes __read_mostly Kirill A. Shutemov
2014-07-29 22:38 ` David Rientjes
2014-08-01 11:51 [PATCH 0/2] faultaround updates Kirill A. Shutemov
2014-08-01 21:32 ` David Rientjes
2014-08-02 8:39 ` Kirill A. Shutemov
2014-08-04 22:20 ` Andrew Morton
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=1406633609-17586-1-git-send-email-kirill.shutemov@linux.intel.com \
--to=kirill.shutemov@linux.intel.com \
--cc=a.ryabinin@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=sasha.levin@oracle.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