From: Konrad Rzeszutek Wilk <konrad@darnok.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Rik van Riel <riel@redhat.com>,
chris.mason@oracle.com, matthew@wil.cx, ngupta@vflare.org,
hannes@cmpxchg.org, hughd@google.com,
sjenning@linux.vnet.ibm.com, JBeulich@novell.com,
dan.magenheimer@oracle.com, linux-mm@kvack.org
Subject: Re: [GIT] (frontswap.v16-tag)
Date: Fri, 1 Jun 2012 16:51:39 -0400 [thread overview]
Message-ID: <CAPbh3rsLrvECi_GPo=zbsJ3Fmip6RE=FoRMdBk3hLKv5aD5=XQ@mail.gmail.com> (raw)
In-Reply-To: <20120529140244.GA3558@phenom.dumpdata.com>
>> No, the real reason is that for new features like this - features that
>> I don't really see myself using personally and that I'm not all that
>> personally excited about - I *really* want others to pipe up with
>> "yes, we're using this, and yes, we want this to be merged".
>>
>> It doesn't seem to be huge, which is great, but the deathly silence of
>> nobody speaking up and saying "yes please", makes me go "ok, I won't
>> pull if nobody speaks up for the feature".
Hey Linus.
A couple of folks here and in the past replies shared their thoughts,
but I don't think I said anything beyond dry technical details.
So I am really really excited about this. I think this
"memory-that-is-not-your-old-memory" is an aspect of technology that
is going to evolve in interesting ways. The same way that SSDs kicked
the notion that "we have tons of milliseconds to do stuff before it
hits the platter" without costing a lot of money, the PCIe memory
cards (or whatever marketing name is used), PCIe inter-machine links,
or even on the embedded side of stuffing more in less, offer fantastic
opportunities. The frontswap provides a means to bridge a lot of these
technologies and share common concepts among them - there is the
compression for the embedded world, there is de-duplication for the
starving virtualization world, there is memory sharing across nodes,
and in my crystal ball I see are those PCIe memory cards being used
too. It is really fun and invigorating and this patchset provides the
basic underpinnings for a lot of it.
So yes please pull!
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/mm.git
stable/frontswap.v16-tag
Thanks!
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-06-01 20:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 20:42 Konrad Rzeszutek Wilk
[not found] ` <20120524202221.GA19856@phenom.dumpdata.com>
2012-05-27 22:29 ` Linus Torvalds
2012-05-29 6:43 ` Jan Beulich
2012-05-29 13:54 ` Seth Jennings
2012-05-29 14:02 ` Konrad Rzeszutek Wilk
2012-05-29 20:49 ` Konrad Rzeszutek Wilk
2012-06-01 20:51 ` Konrad Rzeszutek Wilk [this message]
2012-05-29 14:23 ` Rik van Riel
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='CAPbh3rsLrvECi_GPo=zbsJ3Fmip6RE=FoRMdBk3hLKv5aD5=XQ@mail.gmail.com' \
--to=konrad@darnok.org \
--cc=JBeulich@novell.com \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-mm@kvack.org \
--cc=matthew@wil.cx \
--cc=ngupta@vflare.org \
--cc=riel@redhat.com \
--cc=sjenning@linux.vnet.ibm.com \
--cc=torvalds@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