linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-mm <linux-mm@kvack.org>, linux-fsdevel@vger.kernel.org
Subject: [LSF/MM ATTEND] Memory management
Date: Fri, 10 Jan 2014 18:14:30 +0100	[thread overview]
Message-ID: <52D02A76.50005@suse.cz> (raw)

Hi,

I would like to attend LSF/MM. I'm working in the MM area for half a 
year now, so I'm still learning a lot and hope that the discussions 
would help me clarify longer-term goals to pursue. In general, I'm (of 
course) interested in improving performance where possible, perhaps by 
better use of features the hardware offers. In the past I've been doing 
academic research on performance modeling on shared caches and hope to 
put that experience to use somehow.

During the half year in MM so far, I've been improving performance of 
munlock operations (merged in 3.12), memory compaction effectiveness (in 
mmotm) and recently helping fix the trinity fallout. Currently I 
continue investigating memory compaction with the goal of having similar 
success rates as it used to have around 3.0, but without the associated 
massive performance penalty.

--
Vlastimil Babka
SUSE Labs

--
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-01-10 17:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 17:14 Vlastimil Babka [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-01-05  1:34 [LSF/MM ATTEND] Memory management Wanpeng Li

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=52D02A76.50005@suse.cz \
    --to=vbabka@suse.cz \
    --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).