From: Larry Bassel <lbassel@codeaurora.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Mel Gorman <mgorman@suse.de>,
Larry Bassel <lbassel@codeaurora.org>,
linux-mm@kvack.org, Konrad Wilk <konrad.wilk@oracle.com>
Subject: Re: steering allocations to particular parts of memory
Date: Fri, 21 Sep 2012 10:44:19 -0700 [thread overview]
Message-ID: <20120921174418.GD4018@labbmf01-linux.qualcomm.com> (raw)
In-Reply-To: <9e3b0e01-836d-49d3-8aed-9ed9df6c1cfa@default>
On 17 Sep 12 12:40, Dan Magenheimer wrote:
> Hi Larry --
>
> Sorry I missed seeing you and missed this discussion at Linuxcon!
>
> > based on transcendent memory (which I am somewhat familiar
> > with, having built something based upon it which can be used either
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > as contiguous memory or as clean cache) might work, but
>
> That reminds me... I never saw this code posted on linux-mm
> or lkml or anywhere else. Since this is another interesting
> use of tmem/cleancache/frontswap, it might be good to get
> your work into the kernel or at least into some other public
> tree. Is your code post-able? (re original thread:
> http://www.spinics.net/lists/linux-mm/msg24785.html )
This was done on a 3.0 base (the tmem/zcache was from 3.1) a while back.
Due to the fact that 1) although some benchmarks improved,
very large file system writes suffered performance degradation
(measured with lmdd), 2) it appeared that supporting FAT
(or other filesystems where blocksize != pagesize) would be
difficult and 3) in many use cases we couldn't fill the carved
out FMEM regions with enough cleancache (so memory was still
being "wasted") as well as the fact that there was some functionality
we hadn't yet implemented (mainly supporting non-compressed FMEM) and
that the code would need to be ported forward to our 3.4 source
base, management decided to put this project on the back burner.
Therefore I don't believe I have any relevant code to post
(unless the project is revived and ported to a current source base).
Larry
--
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
--
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>
prev parent reply other threads:[~2012-09-21 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 18:27 steering allocations to particular parts of memory Larry Bassel
2012-09-11 9:34 ` Mel Gorman
2012-09-12 21:28 ` Larry Bassel
2012-09-13 8:34 ` Mel Gorman
2012-09-17 19:40 ` Dan Magenheimer
2012-09-18 8:32 ` Mel Gorman
2012-09-21 17:44 ` Larry Bassel [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=20120921174418.GD4018@labbmf01-linux.qualcomm.com \
--to=lbassel@codeaurora.org \
--cc=dan.magenheimer@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
/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).