From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Russell Pavlicek <russell.pavlicek@citrix.com>,
andres@lagarcavilla.org, tim@xen.org
Cc: "xen-users@lists.xen.org" <xen-users@lists.xen.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Serious issues with xenpaging
Date: Tue, 31 Dec 2013 10:33:30 -0500 [thread overview]
Message-ID: <20131231153330.GC20357@phenom.dumpdata.com> (raw)
In-Reply-To: <55E78A57290FB64FA0D3CF672F9F3DA211C793@SJCPEX01CL03.citrite.net>
On Mon, Dec 23, 2013 at 06:34:55PM +0000, Russell Pavlicek wrote:
> On Twitter, Florian Heigl sent a out a few messages about issues with xenpaging:
>
> ---
> 19-Dec: Anyone successfully use #xen<https://twitter.com/search?q=%23xen&src=hash> #xenpaging<https://twitter.com/search?q=%23xenpaging&src=hash>? docs are at SLES manual, rest is mostly this: http://www.gossamer-threads.com/lists/xen/devel/255798<http://t.co/P36VdL84Et> dead feature or usable?
>
> 22-Dec: @lars_kurth<https://twitter.com/lars_kurth> @RCPavlicek<https://twitter.com/RCPavlicek> Hey guys, I wrote down as much as I could https://piratenpad.de/p/Ik3lOBLniq1L5TEM <https://t.co/e5LQCUD9d0> (since I'm on holiday and not constant online)
>
> 22-Dec: Yay, tested #xen<https://twitter.com/search?q=%23xen&src=hash> Xenpaging (memory overcommit)
> [x] largely untested
> [x] docs outdated
> [x] syntax+logic changed
> [x] broken
> ---
>
> [I've taken the liberty of removing the colorful expletive from the final post]
>
> Is Florian's assessment correct, or is there somewhere we can point him for help? I'm on vacation this week, but if someone replies to me, I will try to forward the information appropriately.
The Maintainers file implies otherwise. Let me CC the maintainers.
>
> Thanks,
>
> Russ Pavlicek
> Xen Project Evangelist, Citrix Systems
> Home Office: +1-301-829-5327
> Mobile: +1-240-397-0199
> UK VoIP: +44 1223 852 894
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-12-31 15:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 18:34 Serious issues with xenpaging Russell Pavlicek
2013-12-31 15:33 ` Konrad Rzeszutek Wilk [this message]
2013-12-31 16:31 ` Tim Deegan
2014-01-03 14:49 ` Andres Lagar-Cavilla
2014-01-03 18:41 ` Konrad Rzeszutek Wilk
2014-01-03 19:51 ` Andres Lagar-Cavilla
2014-01-03 20:31 ` Konrad Rzeszutek Wilk
2014-01-03 21:17 ` Andres Lagar-Cavilla
2014-03-07 15:43 ` Konrad Rzeszutek Wilk
2014-03-07 15:47 ` Andres Lagar-Cavilla
2014-03-07 15:54 ` Olaf Hering
2014-03-07 15:55 ` Andres Lagar-Cavilla
2014-01-06 18:53 ` Olaf Hering
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=20131231153330.GC20357@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=andres@lagarcavilla.org \
--cc=russell.pavlicek@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
--cc=xen-users@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.