All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Dave Jiang <dave.jiang@intel.com>
Cc: akpm@linux-foundation.org, dave.hansen@linux.intel.com,
	mawilcox@microsoft.com, linux-nvdimm@lists.01.org,
	linux-mm@kvack.org, vbabka@suse.cz, jack@suse.com,
	dan.j.williams@intel.com, ross.zwisler@linux.intel.com,
	kirill.shutemov@linux.intel.com
Subject: Re: [PATCH 0/3] 1G transparent hugepage support for device dax
Date: Tue, 24 Jan 2017 12:12:48 +0100	[thread overview]
Message-ID: <20170124111248.GC20153@quack2.suse.cz> (raw)
In-Reply-To: <148521477073.31533.17781371321988910714.stgit@djiang5-desk3.ch.intel.com>

On Mon 23-01-17 16:47:18, Dave Jiang wrote:
> The following series implements support for 1G trasparent hugepage on
> x86 for device dax. The bulk of the code was written by Mathew Wilcox
> a while back supporting transparent 1G hugepage for fs DAX. I have
> forward ported the relevant bits to 4.10-rc. The current submission has
> only the necessary code to support device DAX.

Well, you should really explain why do we want this functionality... Is
anybody going to use it? Why would he want to and what will he gain by
doing so? Because so far I haven't heard of a convincing usecase.

								Honza
> 
> ---
> 
> Dave Jiang (1):
>       dax: Support for transparent PUD pages for device DAX
> 
> Matthew Wilcox (2):
>       mm,fs,dax: Change ->pmd_fault to ->huge_fault
>       mm,x86: Add support for PUD-sized transparent hugepages
> 
> 
>  arch/Kconfig                          |    3 
>  arch/x86/Kconfig                      |    1 
>  arch/x86/include/asm/paravirt.h       |   11 +
>  arch/x86/include/asm/paravirt_types.h |    2 
>  arch/x86/include/asm/pgtable-2level.h |   17 ++
>  arch/x86/include/asm/pgtable-3level.h |   24 +++
>  arch/x86/include/asm/pgtable.h        |  145 +++++++++++++++++++
>  arch/x86/include/asm/pgtable_64.h     |   15 ++
>  arch/x86/kernel/paravirt.c            |    1 
>  arch/x86/mm/pgtable.c                 |   31 ++++
>  drivers/dax/dax.c                     |   82 ++++++++---
>  fs/dax.c                              |   43 ++++--
>  fs/ext2/file.c                        |    2 
>  fs/ext4/file.c                        |    6 -
>  fs/xfs/xfs_file.c                     |   10 +
>  fs/xfs/xfs_trace.h                    |    2 
>  include/asm-generic/pgtable.h         |   75 +++++++++-
>  include/asm-generic/tlb.h             |   14 ++
>  include/linux/dax.h                   |    6 -
>  include/linux/huge_mm.h               |   83 ++++++++++-
>  include/linux/mm.h                    |   40 +++++
>  include/linux/mmu_notifier.h          |   14 ++
>  include/linux/pfn_t.h                 |    8 +
>  mm/gup.c                              |    7 +
>  mm/huge_memory.c                      |  249 +++++++++++++++++++++++++++++++++
>  mm/memory.c                           |  102 ++++++++++++--
>  mm/pagewalk.c                         |   20 +++
>  mm/pgtable-generic.c                  |   14 ++
>  28 files changed, 952 insertions(+), 75 deletions(-)
> 
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

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

  parent reply	other threads:[~2017-01-24 11:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23 23:47 [PATCH 0/3] 1G transparent hugepage support for device dax Dave Jiang
2017-01-23 23:47 ` Dave Jiang
2017-01-23 23:47 ` [PATCH 1/3] mm,fs,dax: Change ->pmd_fault to ->huge_fault Dave Jiang
2017-01-23 23:47   ` Dave Jiang
2017-01-23 23:47 ` [PATCH 2/3] mm, x86: Add support for PUD-sized transparent hugepages Dave Jiang
2017-01-23 23:47   ` Dave Jiang
2017-01-23 23:47 ` [PATCH 3/3] dax: Support for transparent PUD pages for device DAX Dave Jiang
2017-01-23 23:47   ` Dave Jiang
2017-01-24 11:12 ` Jan Kara [this message]
2017-01-24 18:26   ` [PATCH 0/3] 1G transparent hugepage support for device dax Dan Williams
2017-01-24 18:26     ` Dan Williams
2017-01-24 21:24     ` Konrad Rzeszutek Wilk
2017-01-24 21:35       ` Nilesh Choudhury

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=20170124111248.GC20153@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=dave.jiang@intel.com \
    --cc=jack@suse.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-mm@kvack.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=mawilcox@microsoft.com \
    --cc=ross.zwisler@linux.intel.com \
    --cc=vbabka@suse.cz \
    /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.