From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: David Rientjes <rientjes@google.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Hansen <dave.hansen@intel.com>,
Andrey Ryabinin <a.ryabinin@samsung.com>,
Sasha Levin <sasha.levin@oracle.com>,
linux-mm@kvack.org
Subject: Re: [PATCH 0/2] faultaround updates
Date: Sat, 2 Aug 2014 11:39:29 +0300 [thread overview]
Message-ID: <20140802083929.GA17045@node.dhcp.inet.fi> (raw)
In-Reply-To: <alpine.DEB.2.02.1408011432100.11532@chino.kir.corp.google.com>
On Fri, Aug 01, 2014 at 02:32:36PM -0700, David Rientjes wrote:
> On Fri, 1 Aug 2014, Kirill A. Shutemov wrote:
>
> > One fix and one tweak for faultaround code.
> >
> > As alternative, we could just drop debugfs interface and make
> > fault_around_bytes constant.
> >
>
> If we can remove the debugfs interface, then it seems better than
> continuing to support it. Any objections to removing it?
Andrew asked it initially. Up to him.
--
Kirill A. Shutemov
--
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 prev parent reply other threads:[~2014-08-02 8:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 11:51 [PATCH 0/2] faultaround updates Kirill A. Shutemov
2014-08-01 11:51 ` [PATCHv2 1/2] mm: close race between do_fault_around() and fault_around_bytes_set() Kirill A. Shutemov
2014-08-01 21:36 ` Naoya Horiguchi
2014-08-01 11:51 ` [PATCH 2/2] mm: mark fault_around_bytes __read_mostly Kirill A. Shutemov
2014-08-01 21:32 ` [PATCH 0/2] faultaround updates David Rientjes
2014-08-02 8:39 ` Kirill A. Shutemov [this message]
2014-08-04 22:20 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2014-07-29 11:33 Kirill A. Shutemov
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=20140802083929.GA17045@node.dhcp.inet.fi \
--to=kirill@shutemov.name \
--cc=a.ryabinin@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=kirill.shutemov@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.