linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: David Rientjes <rientjes@google.com>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	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: Mon, 4 Aug 2014 15:20:59 -0700	[thread overview]
Message-ID: <20140804152059.fc9effe1989072d37214ab7f@linux-foundation.org> (raw)
In-Reply-To: <20140802083929.GA17045@node.dhcp.inet.fi>

On Sat, 2 Aug 2014 11:39:29 +0300 "Kirill A. Shutemov" <kirill@shutemov.name> wrote:

> 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.

Well, we had a bunch of magic constants in there which may not be
optimized.  The idea is to make them tunable so that interested parties
can determine the best settings without having to rebuild the kernel. 
Once that's all done we can remove the tunable (because it's debugfs)
and hard-wire the optimised constants.

But I don't think anyone has done this tuning work yet.

--
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>

  reply	other threads:[~2014-08-04 22:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-01 11:51 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
2014-08-04 22:20     ` Andrew Morton [this message]
  -- 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=20140804152059.fc9effe1989072d37214ab7f@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=a.ryabinin@samsung.com \
    --cc=dave.hansen@intel.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=kirill@shutemov.name \
    --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