From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Konrad Rzeszutek Wilk <konrad@kernel.org>,
bob.liu@oracle.com, dan.magenheimer@oracle.com,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
linux-mm@kvack.org, xen-devel@lists.xensource.com
Subject: RE: [PATCH] Fixes, cleanups, compile warning fixes, and documentation update for Xen tmem driver (v2).
Date: Wed, 15 May 2013 10:22:11 -0700 (PDT) [thread overview]
Message-ID: <76ac8597-9be3-44fd-a3d5-39c6130a171a@default> (raw)
In-Reply-To: <<1368554966-30469-1-git-send-email-konrad.wilk@oracle.com>>
> From: Konrad Rzeszutek [mailto:ketuzsezr@gmail.com] On Behalf Of Konrad Rzeszutek Wilk
> Sent: Tuesday, May 14, 2013 12:09 PM
> To: bob.liu@oracle.com; dan.magenheimer@oracle.com; linux-kernel@vger.kernel.org; akpm@linux-
> foundation.org; linux-mm@kvack.org; xen-devel@lists.xensource.com
> Subject: [PATCH] Fixes, cleanups, compile warning fixes, and documentation update for Xen tmem driver
> (v2).
>
> Heya,
>
> These nine patches fix the tmem driver to:
> - not emit a compile warning anymore (reported by 0 day test compile tool)
> - remove the various nofrontswap, nocleancache, noselfshrinking, noselfballooning,
> selfballooning, selfshrinking bootup options.
> - said options are now folded in the tmem driver as module options and are
> much shorter (and also there are only four of them now).
> - add documentation to explain these parameters in kernel-parameters.txt
> - And lastly add some logic to not enable selfshrinking and selfballooning
> if frontswap functionality is off.
>
> That is it. Tested and ready to go. If nobody objects will put on my queue
> for Linus on Monday.
FWIW, I've scanned all of these and they look sane and good. So consider all:
Acked-by: Dan Magenheimer <dan.magenheimer@oracle.com>
> Documentation/kernel-parameters.txt | 21 ++++++++
> drivers/xen/Kconfig | 7 +--
> drivers/xen/tmem.c | 87 ++++++++++++++++-------------------
> drivers/xen/xen-selfballoon.c | 47 ++----------------
> 4 files changed, 69 insertions(+), 93 deletions(-)
>
> (oh nice, more deletions!)
>
> Konrad Rzeszutek Wilk (9):
> xen/tmem: Cleanup. Remove the parts that say temporary.
> xen/tmem: Move all of the boot and module parameters to the top of the file.
> xen/tmem: Split out the different module/boot options.
> xen/tmem: Fix compile warning.
> xen/tmem: s/disable_// and change the logic.
> xen/tmem: Remove the boot options and fold them in the tmem.X parameters.
> xen/tmem: Remove the usage of 'noselfshrink' and use 'tmem.selfshrink' bool instead.
> xen/tmem: Remove the usage of '[no|]selfballoon' and use 'tmem.selfballooning' bool instead.
> xen/tmem: Don't use self[ballooning|shrinking] if frontswap is off.
--
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 parent reply other threads:[~2013-05-15 17:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<1368554966-30469-1-git-send-email-konrad.wilk@oracle.com>
2013-05-15 17:22 ` Dan Magenheimer [this message]
2013-05-14 18:09 Konrad Rzeszutek Wilk
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=76ac8597-9be3-44fd-a3d5-39c6130a171a@default \
--to=dan.magenheimer@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bob.liu@oracle.com \
--cc=konrad@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=xen-devel@lists.xensource.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