linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [LSF/MM ATTEND] MM track: Memory encryption, THP
Date: Tue, 19 Feb 2019 17:59:24 +0300	[thread overview]
Message-ID: <20190219145924.olggllneomorpenu@kshutemo-mobl1> (raw)

Hi,

I would like to attend upcoming summit.

I was not very active in generic memory managment field last year. I hope
it will change this year.

I'm still interested in moving THP forward and I see there is a number of
THP-related topics proposed for the summit. I would like to participate in
the discussion (and hopefully contribute something).

The other topic I would like to discuss is memory encryption and userspace
APIs for it. See Dave's topic proposal[1].

[1] https://lore.kernel.org/linux-mm/788d7050-f6bb-b984-69d9-504056e6c5a6@intel.com

-- 
 Kirill A. Shutemov


                 reply	other threads:[~2019-02-19 14:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20190219145924.olggllneomorpenu@kshutemo-mobl1 \
    --to=kirill@shutemov.name \
    --cc=linux-kernel@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