linux-kernel - [GIT PULL] xen: tmem: self-ballooning and frontswap-selfshriking

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Thu, 30 Jun 2011 14:41:06 -0700 (PDT)
From:	Dan Magenheimer <dan.magenheimer@...cle.com>
To:	Konrad Wilk <konrad.wilk@...cle.com>
Cc:	linux-kernel@...r.kernel.org, xen-devel@...ts.xensource.com
Subject: [GIT PULL] xen: tmem: self-ballooning and frontswap-selfshriking

Hi Konrad --

Please pull the following branch into your Xen for-linus tree
for the upcoming 3.1 window.

git://git.kernel.org/pub/scm/linux/kernel/git/djm/tmem.git #xen-tmem-selfballoon-v3

The branch is based off of 3.0-rc1.

This single commit introduces two in-kernel drivers for Xen
transcendent memory ("tmem") that complement cleancache and
frontswap.  Both use control theory to dynamically adjust and
optimize memory utilization.  Much more detail is in the
header comment of the file.

Diffstat:
 drivers/xen/Kconfig                      |   12 
 drivers/xen/Makefile                     |    1 
 drivers/xen/xen-balloon.c                |    2 
 drivers/xen/xen-selfballoon.c            |  429 +++++++++++++++++++++
 include/xen/balloon.h                    |   10 
 include/xen/tmem.h                       |    5 
 6 files changed, 459 insertions(+)

Dan Magenheimer (1):
      xen: tmem: self-ballooning and frontswap self-shrinking

Note that this patch has a slight build dependency on last week's:

afec6e04922d0c8c7e244be2e544bac5e7e36294 xen: prepare tmem shim to handle frontswap

in your devel/next-3.0 branch (because tmem_enabled is EXPORT_SYM'ed
in that commit and extern'ed in a file in this commit).  I don't
think this is a problem as you've already pushed that commit
to linux-next, but am noting the dependency in case some kind
of commit reordering were to occur.

Thanks,
Dan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/