From: Dan Magenheimer <dan.magenheimer@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Konrad Wilk <konrad.wilk@oracle•com>
Subject: RE: next phase of tmem into linux-next
Date: Wed, 1 Jun 2011 09:22:59 -0700 (PDT) [thread overview]
Message-ID: <dedd3fa5-5dc3-4ce1-9ab4-dc77e23a6d7d@default> (raw)
In-Reply-To: <20110601142544.62494a52.sfr@canb.auug.org.au>
> On Tue, 31 May 2011 17:49:21 -0700 (PDT) Dan Magenheimer
> <dan.magenheimer@oracle•com> wrote:
> >
> > Please re-include the following tree into linux-next. The
> > commit series is for frontswap, the complement of cleancache
> > handling swap pages, which is the next phase in tmem. It also
> > includes the shim code to Xen tmem for frontswap. It applies
> > cleanly on linux-3.0-rc1, but if there are any problems or
> > you have any questions, please let me know!
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/djm/tmem.git#linux-next
>
> I don't remove trees from linux-next unless excplictly asked to, so
> this
> tree is still included
Hi Stephen --
OK, I see "Already up-to-date" in merge.log. I'll assume
that the new frontswap commits will lag a day. (Thanks,
Konrad, for helping me find this info and pointing out the
probable lag.)
(A thought... perhaps the merge.log generation script should
do a "date" at the beginning and end, so one knows if one
has just missed your merge window?)
> As long as you stick to the rules (posted,
> reviewed, ready for Linus), anything you add to that tree will be
> included.
Yep, understood. Frontswap has been posted on lkml and tested for
over a year (and for nearly 2-1/2 years if counting earlier
versions as part of the original tmem postings), but hasn't gotten
as much attention because it was serialized behind merging of cleancache.
> The tree is still called "cleancache" in linux-next. Should I change
> that to something more generic?
Yes please. A good short name would be "tmem", but if you want
something longer and more descriptive maybe, "transcendent_memory".
I expect in the future that this might be the path for, for
example, tmem-related code that is promoted from drivers/staging.
E.g., the generic tmem.c code in drivers/staging/zcache could
probably end up in lib at some point if/when there are multiple users.
Thanks!
Dan
next prev parent reply other threads:[~2011-06-01 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 0:49 next phase of tmem into linux-next Dan Magenheimer
2011-06-01 4:25 ` Stephen Rothwell
2011-06-01 16:22 ` Dan Magenheimer [this message]
2011-06-01 23:48 ` Stephen Rothwell
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=dedd3fa5-5dc3-4ce1-9ab4-dc77e23a6d7d@default \
--to=dan.magenheimer@oracle$(echo .)com \
--cc=konrad.wilk@oracle$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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