linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrea Arcangeli <aarcange@redhat.com>
To: Hugh Dickins <hughd@google.com>
Cc: lsf-pc@lists.linux-foundation.org,
	"Kirill A. Shutemov" <kirill@shutemov.name>,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Subject: Re: [LSF/MM ATTEND] Transparent huge pages: huge tmpfs
Date: Fri, 16 Jan 2015 14:12:35 +0100	[thread overview]
Message-ID: <20150116131235.GW6103@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1501152301470.7987@eggly.anvils>

Hello,

On Thu, Jan 15, 2015 at 11:54:09PM -0800, Hugh Dickins wrote:
> I would like to attend LSF/MM this year; and most of all would like
> to join Kirill Shutemov in his discussion of THP refcounting etc.

Seconded.

I'm positive about the tradeoffs coming from Kirill's simplification
of the THP refcounting by allowing to map compound pages in ptes (not
only in trans_huge_pmds) and in turn by relaxing the constraint that
split_huge_page cannot fail. It looks a worthwhile change even if it
spreads the complexity to a wider codebase and it doesn't keep it
localized in get_page/put_page anymore.

> I admit that I have not yet studied his refcounting patchset, but
> shall have done so by March.  I've been fully occupied these last
> few months with an alternative approach to THPage cache, huge tmpfs:
> starting from my belief that compound pages were ideal for hugetlbfs,
> questionable for anonymous THP, completely unsuited to THPage cache.
> 
> We shall try to work out how much we have in common, and where to go
> from there.
> 
> Huge tmpfs is currently implemented on Google's not-so-modern kernel.
> I intend to port it to v3.19 and post before LSF; but if that ends up
> like a night-before-the-conference dump of XXX patches, no, I'll spare
> you and spend more time looking at other people's work instead.

I'm interested the above topics too.

Thanks and hope to see you soon :)
Andrea

--
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:[~2015-01-16 13:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16  7:54 [LSF/MM ATTEND] Transparent huge pages: huge tmpfs Hugh Dickins
2015-01-16 12:18 ` Kirill A. Shutemov
2015-01-16 13:12 ` Andrea Arcangeli [this message]

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=20150116131235.GW6103@redhat.com \
    --to=aarcange@redhat.com \
    --cc=hughd@google.com \
    --cc=kirill@shutemov.name \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.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).