From: Christoph Lameter <cl@linux.com>
To: linux-mm@kvack.org
Cc: Jesper Dangaard Brouer <brouer@redhat.com>,
riel@redhat.com, Mel Gorman <mel@csn.ul.ie>
Subject: [LSF/MM TOPIC] Movable memory and reliable higher order allocations
Date: Tue, 28 Feb 2017 15:32:12 -0600 (CST) [thread overview]
Message-ID: <alpine.DEB.2.20.1702281526170.31946@east.gentwo.org> (raw)
This has come up lots of times. We talked about this at linux.conf.au
again and agreed to try to make the radix tree movable. Sadly I have not
had enough time yet to make progress on this one but reliable higher order
allocations or some sort of other solution are needed for performance
reasons in many places. Recently there was demand from the developers in
the network stack and in the RDMA subsystems for large contiguous
allocation for performance reasons. I would like to talk about this (yes
the gazillionth time) to see what avenues there are to make progress on
this one.
--
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>
next reply other threads:[~2017-02-28 21:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 21:32 Christoph Lameter [this message]
2017-02-28 23:17 ` [LSF/MM TOPIC] Movable memory and reliable higher order allocations Matthew Wilcox
2017-03-02 4:12 ` Matthew Wilcox
2017-03-02 17:26 ` Christoph Lameter
2017-03-02 20:55 ` Matthew Wilcox
2017-03-03 15:24 ` Christoph Lameter
2017-03-03 20:39 ` Matthew Wilcox
2017-03-06 14:53 ` Christoph Lameter
2017-03-02 17:00 ` Christoph Lameter
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=alpine.DEB.2.20.1702281526170.31946@east.gentwo.org \
--to=cl@linux.com \
--cc=brouer@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=riel@redhat.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;
as well as URLs for NNTP newsgroup(s).