From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell Pavlicek Subject: Serious issues with xenpaging Date: Mon, 23 Dec 2013 18:34:55 +0000 Message-ID: <55E78A57290FB64FA0D3CF672F9F3DA211C793@SJCPEX01CL03.citrite.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============9044720443905162173==" Return-path: Content-Language: en-US List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org --===============9044720443905162173== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_55E78A57290FB64FA0D3CF672F9F3DA211C793SJCPEX01CL03citri_" --_000_55E78A57290FB64FA0D3CF672F9F3DA211C793SJCPEX01CL03citri_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On Twitter, Florian Heigl sent a out a few messages about issues with xenpa= ging: --- 19-Dec: Anyone successfully use #xen #xenpaging? docs are at SLES manual, rest is mostly this: http://www.gossamer-thre= ads.com/lists/xen/devel/255798 dead feature or usab= le? 22-Dec: @lars_kurth @RCPavlicek Hey guys, I wrote down as much as I could https://pira= tenpad.de/p/Ik3lOBLniq1L5TEM (since I'm on holi= day and not constant online) 22-Dec: Yay, tested #xen = 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 p= ost] 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. 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 --_000_55E78A57290FB64FA0D3CF672F9F3DA211C793SJCPEX01CL03citri_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
On Twitter, Florian Heigl sent a out a few messages about issues wit= h xenpaging:

---
19-Dec: Anyone successfully use #xen #xenpaging? docs are at SLES manual, res= t is mostly this: http://www.gossamer-threads.com/lists/xen/devel/255798 dead feature or usable?

22-Dec: @lars_kurth @RCPavlicek Hey guys, I wrote down as much as I could https://piratenpad.de/p/Ik3lOBLniq1L5TEM   (since I'm o= n holiday and not constant online)

22-Dec: Yay, tested #xen 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 p= ost]

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 wil= l try to forward the information appropriately.

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
--_000_55E78A57290FB64FA0D3CF672F9F3DA211C793SJCPEX01CL03citri_-- --===============9044720443905162173== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============9044720443905162173==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Serious issues with xenpaging Date: Tue, 31 Dec 2013 10:33:30 -0500 Message-ID: <20131231153330.GC20357@phenom.dumpdata.com> References: <55E78A57290FB64FA0D3CF672F9F3DA211C793@SJCPEX01CL03.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <55E78A57290FB64FA0D3CF672F9F3DA211C793@SJCPEX01CL03.citrite.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Russell Pavlicek , andres@lagarcavilla.org, tim@xen.org Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org 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 #xenpaging? docs are at SLES manual, rest is mostly this: http://www.gossamer-threads.com/lists/xen/devel/255798 dead feature or usable? > > 22-Dec: @lars_kurth @RCPavlicek Hey guys, I wrote down as much as I could https://piratenpad.de/p/Ik3lOBLniq1L5TEM (since I'm on holiday and not constant online) > > 22-Dec: Yay, tested #xen 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tim Deegan Subject: Re: Serious issues with xenpaging Date: Tue, 31 Dec 2013 17:31:10 +0100 Message-ID: <20131231163110.GA34150@deinos.phlegethon.org> References: <55E78A57290FB64FA0D3CF672F9F3DA211C793@SJCPEX01CL03.citrite.net> <20131231153330.GC20357@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20131231153330.GC20357@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Konrad Rzeszutek Wilk Cc: "xen-users@lists.xen.org" , Russell Pavlicek , Olaf Hering , andres@lagarcavilla.org, "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org At 10:33 -0500 on 31 Dec (1388482410), Konrad Rzeszutek Wilk wrote: > 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 #xenpaging? docs are at SLES manual, rest is mostly this: http://www.gossamer-threads.com/lists/xen/devel/255798 dead feature or usable? > > > > 22-Dec: @lars_kurth @RCPavlicek Hey guys, I wrote down as much as I could https://piratenpad.de/p/Ik3lOBLniq1L5TEM (since I'm on holiday and not constant online) > > > > 22-Dec: Yay, tested #xen 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. Andres really owns this code, so I'll punt to him for an official answer, but: - It's been listed as a 'tech preview' on the feature list since it went in. http://wiki.xenproject.org/wiki/Xen_Release_Features says: "Preview, due to limited tools support. Hypervisor side in good shape." - I can't say anything about SuSE's apparent support for it, except that ISTR Olaf worked at/for/with SuSE at the time. - Patches would, of course, be welcome. Tim. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andres Lagar-Cavilla Subject: Re: Serious issues with xenpaging Date: Fri, 3 Jan 2014 09:49:36 -0500 Message-ID: <556C4AC0-F10F-4977-8FCD-3129E416B062@gridcentric.ca> References: <55E78A57290FB64FA0D3CF672F9F3DA211C793@SJCPEX01CL03.citrite.net> <20131231153330.GC20357@phenom.dumpdata.com> <20131231163110.GA34150@deinos.phlegethon.org> Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20131231163110.GA34150@deinos.phlegethon.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Tim Deegan Cc: Olaf Hering , "xen-devel@lists.xen.org" , andres@lagarcavilla.org, "xen-users@lists.xen.org" , Russell Pavlicek List-Id: xen-devel@lists.xenproject.org On Dec 31, 2013, at 11:31 AM, Tim Deegan wrote: > At 10:33 -0500 on 31 Dec (1388482410), Konrad Rzeszutek Wilk wrote: >> 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 x= enpaging: >>> = >>> --- >>> 19-Dec: Anyone successfully use #xen #xenpaging? docs are at SLES manual, rest is mostly this: http://www.gossamer= -threads.com/lists/xen/devel/255798 dead feature or= usable? >>> = >>> 22-Dec: @lars_kurth @RCPavlicek Hey guys, I wrote down as much as I could https://= piratenpad.de/p/Ik3lOBLniq1L5TEM (since I'm on = holiday and not constant online) >>> = >>> 22-Dec: Yay, tested #xen 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 fin= al 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. > = > Andres really owns this code, so I'll punt to him for an official > answer, but: The part actively maintained is the hypervisor support for paging, and the = interface. tools/xenpaging is one way to consume that interface. It seems to have suff= ered from bitrot. So other than echoing Tim's points below, I'll add - Some interesting ideas thrown around by Florian in his notes. Could lead = to a robust discussion in xen-devel =85 if Florian is still interested. - Perhaps the developers who are interested (myself included) should make a= decent effort at improving the in-tree tools. There is the argument that f= or example KSM gives KVM users a sharing solution that just works, whether = you like the results or not. In that vein xenpaging apparently doesn't cut = it, nor the absence of a basic sharing tool. One simple paging tool could be lazy restore. There is some interest out th= ere, it would be relatively straightforward to codify. Andres > = > - It's been listed as a 'tech preview' on the feature list since it went > in. http://wiki.xenproject.org/wiki/Xen_Release_Features says: > "Preview, due to limited tools support. Hypervisor side in good shape." > = > - I can't say anything about SuSE's apparent support for it, except > that ISTR Olaf worked at/for/with SuSE at the time. > = > - Patches would, of course, be welcome. > = > Tim. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Serious issues with xenpaging Date: Fri, 3 Jan 2014 13:41:54 -0500 Message-ID: <20140103184154.GA29283@phenom.dumpdata.com> References: <55E78A57290FB64FA0D3CF672F9F3DA211C793@SJCPEX01CL03.citrite.net> <20131231153330.GC20357@phenom.dumpdata.com> <20131231163110.GA34150@deinos.phlegethon.org> <556C4AC0-F10F-4977-8FCD-3129E416B062@gridcentric.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: Content-Disposition: inline In-Reply-To: <556C4AC0-F10F-4977-8FCD-3129E416B062@gridcentric.ca> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andres Lagar-Cavilla Cc: Olaf Hering , Tim Deegan , "xen-devel@lists.xen.org" , andres@lagarcavilla.org, "xen-users@lists.xen.org" , Russell Pavlicek List-Id: xen-devel@lists.xenproject.org T24gRnJpLCBKYW4gMDMsIDIwMTQgYXQgMDk6NDk6MzZBTSAtMDUwMCwgQW5kcmVzIExhZ2FyLUNh dmlsbGEgd3JvdGU6Cj4gCj4gT24gRGVjIDMxLCAyMDEzLCBhdCAxMTozMSBBTSwgVGltIERlZWdh biA8dGltQHhlbi5vcmc+IHdyb3RlOgo+IAo+ID4gQXQgMTA6MzMgLTA1MDAgb24gMzEgRGVjICgx Mzg4NDgyNDEwKSwgS29ucmFkIFJ6ZXN6dXRlayBXaWxrIHdyb3RlOgo+ID4+IE9uIE1vbiwgRGVj IDIzLCAyMDEzIGF0IDA2OjM0OjU1UE0gKzAwMDAsIFJ1c3NlbGwgUGF2bGljZWsgd3JvdGU6Cj4g Pj4+IE9uIFR3aXR0ZXIsIEZsb3JpYW4gSGVpZ2wgc2VudCBhIG91dCBhIGZldyBtZXNzYWdlcyBh Ym91dCBpc3N1ZXMgd2l0aCB4ZW5wYWdpbmc6Cj4gPj4+IAo+ID4+PiAtLS0KPiA+Pj4gMTktRGVj OiBBbnlvbmUgc3VjY2Vzc2Z1bGx5IHVzZSAjeGVuPGh0dHBzOi8vdHdpdHRlci5jb20vc2VhcmNo P3E9JTIzeGVuJnNyYz1oYXNoPiAjeGVucGFnaW5nPGh0dHBzOi8vdHdpdHRlci5jb20vc2VhcmNo P3E9JTIzeGVucGFnaW5nJnNyYz1oYXNoPj8gZG9jcyBhcmUgYXQgU0xFUyBtYW51YWwsIHJlc3Qg aXMgbW9zdGx5IHRoaXM6IGh0dHA6Ly93d3cuZ29zc2FtZXItdGhyZWFkcy5jb20vbGlzdHMveGVu L2RldmVsLzI1NTc5ODxodHRwOi8vdC5jby9QMzZWZEw4NEV0PiBkZWFkIGZlYXR1cmUgb3IgdXNh YmxlPwo+ID4+PiAKPiA+Pj4gMjItRGVjOiBAbGFyc19rdXJ0aDxodHRwczovL3R3aXR0ZXIuY29t L2xhcnNfa3VydGg+IEBSQ1BhdmxpY2VrPGh0dHBzOi8vdHdpdHRlci5jb20vUkNQYXZsaWNlaz4g SGV5IGd1eXMsIEkgd3JvdGUgZG93biBhcyBtdWNoIGFzIEkgY291bGQgaHR0cHM6Ly9waXJhdGVu cGFkLmRlL3AvSWszbE9CTG5pcTFMNVRFTSAgIDxodHRwczovL3QuY28vZTVMUUNVRDlkMD4gKHNp bmNlIEknbSBvbiBob2xpZGF5IGFuZCBub3QgY29uc3RhbnQgb25saW5lKQo+ID4+PiAKPiA+Pj4g MjItRGVjOiBZYXksIHRlc3RlZCAjeGVuPGh0dHBzOi8vdHdpdHRlci5jb20vc2VhcmNoP3E9JTIz eGVuJnNyYz1oYXNoPiBYZW5wYWdpbmcgKG1lbW9yeSBvdmVyY29tbWl0KQo+ID4+PiBbeF0gbGFy Z2VseSB1bnRlc3RlZAo+ID4+PiBbeF0gZG9jcyBvdXRkYXRlZAo+ID4+PiBbeF0gc3ludGF4K2xv Z2ljIGNoYW5nZWQKPiA+Pj4gW3hdIGJyb2tlbgo+ID4+PiAtLS0KPiA+Pj4gCj4gPj4+IFtJJ3Zl IHRha2VuIHRoZSBsaWJlcnR5IG9mIHJlbW92aW5nIHRoZSBjb2xvcmZ1bCBleHBsZXRpdmUgZnJv bSB0aGUgZmluYWwgcG9zdF0KPiA+Pj4gCj4gPj4+IElzIEZsb3JpYW4ncyBhc3Nlc3NtZW50IGNv cnJlY3QsIG9yIGlzIHRoZXJlIHNvbWV3aGVyZSB3ZSBjYW4gcG9pbnQgaGltIGZvciBoZWxwPyAg SSdtIG9uIHZhY2F0aW9uIHRoaXMgd2VlaywgYnV0IGlmIHNvbWVvbmUgcmVwbGllcyB0byBtZSwg SSB3aWxsIHRyeSB0byBmb3J3YXJkIHRoZSBpbmZvcm1hdGlvbiBhcHByb3ByaWF0ZWx5Lgo+ID4+ IAo+ID4+IFRoZSBNYWludGFpbmVycyBmaWxlIGltcGxpZXMgb3RoZXJ3aXNlLiBMZXQgbWUgQ0Mg dGhlIG1haW50YWluZXJzLgo+ID4gCj4gPiBBbmRyZXMgcmVhbGx5IG93bnMgdGhpcyBjb2RlLCBz byBJJ2xsIHB1bnQgdG8gaGltIGZvciBhbiBvZmZpY2lhbAo+ID4gYW5zd2VyLCBidXQ6Cj4gVGhl IHBhcnQgYWN0aXZlbHkgbWFpbnRhaW5lZCBpcyB0aGUgaHlwZXJ2aXNvciBzdXBwb3J0IGZvciBw YWdpbmcsIGFuZCB0aGUgaW50ZXJmYWNlLgo+IAo+IHRvb2xzL3hlbnBhZ2luZyBpcyBvbmUgd2F5 IHRvIGNvbnN1bWUgdGhhdCBpbnRlcmZhY2UuIEl0IHNlZW1zIHRvIGhhdmUgc3VmZmVyZWQgZnJv bSBiaXRyb3QuCgpXaGF0IGlzIHRoZSBvdGhlciBpbnRlcmZhY2U/IFRoYW5rcyEKPiAKPiBTbyBv dGhlciB0aGFuIGVjaG9pbmcgVGltJ3MgcG9pbnRzIGJlbG93LCBJJ2xsIGFkZAo+IAo+IC0gU29t ZSBpbnRlcmVzdGluZyBpZGVhcyB0aHJvd24gYXJvdW5kIGJ5IEZsb3JpYW4gaW4gaGlzIG5vdGVz LiBDb3VsZCBsZWFkIHRvIGEgcm9idXN0IGRpc2N1c3Npb24gaW4geGVuLWRldmVsIOKApiBpZiBG bG9yaWFuIGlzIHN0aWxsIGludGVyZXN0ZWQuCj4gCj4gLSBQZXJoYXBzIHRoZSBkZXZlbG9wZXJz IHdobyBhcmUgaW50ZXJlc3RlZCAobXlzZWxmIGluY2x1ZGVkKSBzaG91bGQgbWFrZSBhIGRlY2Vu dCBlZmZvcnQgYXQgaW1wcm92aW5nIHRoZSBpbi10cmVlIHRvb2xzLiBUaGVyZSBpcyB0aGUgYXJn dW1lbnQgdGhhdCBmb3IgZXhhbXBsZSBLU00gZ2l2ZXMgS1ZNIHVzZXJzIGEgc2hhcmluZyBzb2x1 dGlvbiB0aGF0IGp1c3Qgd29ya3MsIHdoZXRoZXIgeW91IGxpa2UgdGhlIHJlc3VsdHMgb3Igbm90 LiBJbiB0aGF0IHZlaW4geGVucGFnaW5nIGFwcGFyZW50bHkgZG9lc24ndCBjdXQgaXQsIG5vciB0 aGUgYWJzZW5jZSBvZiBhIGJhc2ljIHNoYXJpbmcgdG9vbC4KPiAKPiBPbmUgc2ltcGxlIHBhZ2lu ZyB0b29sIGNvdWxkIGJlIGxhenkgcmVzdG9yZS4gVGhlcmUgaXMgc29tZSBpbnRlcmVzdCBvdXQg dGhlcmUsIGl0IHdvdWxkIGJlIHJlbGF0aXZlbHkgc3RyYWlnaHRmb3J3YXJkIHRvIGNvZGlmeS4K PiAKPiBBbmRyZXMKPiA+IAo+ID4gLSBJdCdzIGJlZW4gbGlzdGVkIGFzIGEgJ3RlY2ggcHJldmll dycgb24gdGhlIGZlYXR1cmUgbGlzdCBzaW5jZSBpdCB3ZW50Cj4gPiAgaW4uICBodHRwOi8vd2lr aS54ZW5wcm9qZWN0Lm9yZy93aWtpL1hlbl9SZWxlYXNlX0ZlYXR1cmVzIHNheXM6Cj4gPiAgIlBy ZXZpZXcsIGR1ZSB0byBsaW1pdGVkIHRvb2xzIHN1cHBvcnQuIEh5cGVydmlzb3Igc2lkZSBpbiBn b29kIHNoYXBlLiIKPiA+IAo+ID4gLSBJIGNhbid0IHNheSBhbnl0aGluZyBhYm91dCBTdVNFJ3Mg YXBwYXJlbnQgc3VwcG9ydCBmb3IgaXQsIGV4Y2VwdAo+ID4gIHRoYXQgSVNUUiBPbGFmIHdvcmtl ZCBhdC9mb3Ivd2l0aCBTdVNFIGF0IHRoZSB0aW1lLgo+ID4gCj4gPiAtIFBhdGNoZXMgd291bGQs IG9mIGNvdXJzZSwgYmUgd2VsY29tZS4KPiA+IAo+ID4gVGltLgo+IAoKX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVsIG1haWxpbmcgbGlzdApY ZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy94ZW4tZGV2ZWwK From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andres Lagar-Cavilla Subject: Re: Serious issues with xenpaging Date: Fri, 3 Jan 2014 14:51:14 -0500 Message-ID: References: <55E78A57290FB64FA0D3CF672F9F3DA211C793@SJCPEX01CL03.citrite.net> <20131231153330.GC20357@phenom.dumpdata.com> <20131231163110.GA34150@deinos.phlegethon.org> <556C4AC0-F10F-4977-8FCD-3129E416B062@gridcentric.ca> <20140103184154.GA29283@phenom.dumpdata.com> Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20140103184154.GA29283@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Konrad Rzeszutek Wilk Cc: Olaf Hering , Andres Lagar-Cavilla , Tim Deegan , "xen-devel@lists.xen.org" , andres@lagarcavilla.org, "xen-users@lists.xen.org" , Russell Pavlicek List-Id: xen-devel@lists.xenproject.org On Jan 3, 2014, at 1:41 PM, Konrad Rzeszutek Wilk = wrote: > On Fri, Jan 03, 2014 at 09:49:36AM -0500, Andres Lagar-Cavilla wrote: >> = >> On Dec 31, 2013, at 11:31 AM, Tim Deegan wrote: >> = >>> At 10:33 -0500 on 31 Dec (1388482410), Konrad Rzeszutek Wilk wrote: >>>> 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 #xenpaging? docs are at SLES manual, rest is mostly this: http://www.gossame= r-threads.com/lists/xen/devel/255798 dead feature o= r usable? >>>>> = >>>>> 22-Dec: @lars_kurth @RCPavlicek Hey guys, I wrote down as much as I could https:= //piratenpad.de/p/Ik3lOBLniq1L5TEM (since I'm o= n holiday and not constant online) >>>>> = >>>>> 22-Dec: Yay, tested #xen 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 f= inal post] >>>>> = >>>>> Is Florian's assessment correct, or is there somewhere we can point h= im for help? I'm on vacation this week, but if someone replies to me, I wi= ll try to forward the information appropriately. >>>> = >>>> The Maintainers file implies otherwise. Let me CC the maintainers. >>> = >>> Andres really owns this code, so I'll punt to him for an official >>> answer, but: >> The part actively maintained is the hypervisor support for paging, and t= he interface. >> = >> tools/xenpaging is one way to consume that interface. It seems to have s= uffered from bitrot. > = > What is the other interface? Thanks! Not sure what the question is. There is one interface. What I was referring= to, is that tools/xenpaging implements one specific paging policy: victim = selection, rate limiting, paging target, all of these are algorithms that e= ntirely define what bang for your money you will get. Andres >> = >> So other than echoing Tim's points below, I'll add >> = >> - Some interesting ideas thrown around by Florian in his notes. Could le= ad to a robust discussion in xen-devel =85 if Florian is still interested. >> = >> - Perhaps the developers who are interested (myself included) should mak= e a decent effort at improving the in-tree tools. There is the argument tha= t for example KSM gives KVM users a sharing solution that just works, wheth= er you like the results or not. In that vein xenpaging apparently doesn't c= ut it, nor the absence of a basic sharing tool. >> = >> One simple paging tool could be lazy restore. There is some interest out= there, it would be relatively straightforward to codify. >> = >> Andres >>> = >>> - It's been listed as a 'tech preview' on the feature list since it went >>> in. http://wiki.xenproject.org/wiki/Xen_Release_Features says: >>> "Preview, due to limited tools support. Hypervisor side in good shape." >>> = >>> - I can't say anything about SuSE's apparent support for it, except >>> that ISTR Olaf worked at/for/with SuSE at the time. >>> = >>> - Patches would, of course, be welcome. >>> = >>> Tim. >> = From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Serious issues with xenpaging Date: Fri, 3 Jan 2014 15:31:39 -0500 Message-ID: <20140103203139.GA2570@phenom.dumpdata.com> References: <55E78A57290FB64FA0D3CF672F9F3DA211C793@SJCPEX01CL03.citrite.net> <20131231153330.GC20357@phenom.dumpdata.com> <20131231163110.GA34150@deinos.phlegethon.org> <556C4AC0-F10F-4977-8FCD-3129E416B062@gridcentric.ca> <20140103184154.GA29283@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andres Lagar-Cavilla Cc: Olaf Hering , Tim Deegan , "xen-devel@lists.xen.org" , andres@lagarcavilla.org, "xen-users@lists.xen.org" , Russell Pavlicek List-Id: xen-devel@lists.xenproject.org On Fri, Jan 03, 2014 at 02:51:14PM -0500, Andres Lagar-Cavilla wrote: > On Jan 3, 2014, at 1:41 PM, Konrad Rzeszutek Wilk wrote: > > > On Fri, Jan 03, 2014 at 09:49:36AM -0500, Andres Lagar-Cavilla wrote: > >> > >> On Dec 31, 2013, at 11:31 AM, Tim Deegan wrote: > >> > >>> At 10:33 -0500 on 31 Dec (1388482410), Konrad Rzeszutek Wilk wrote: > >>>> 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 #xenpaging? docs are at SLES manual, rest is mostly this: http://www.gossamer-threads.com/lists/xen/devel/255798 dead feature or usable? > >>>>> > >>>>> 22-Dec: @lars_kurth @RCPavlicek Hey guys, I wrote down as much as I could https://piratenpad.de/p/Ik3lOBLniq1L5TEM (since I'm on holiday and not constant online) > >>>>> > >>>>> 22-Dec: Yay, tested #xen 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. > >>> > >>> Andres really owns this code, so I'll punt to him for an official > >>> answer, but: > >> The part actively maintained is the hypervisor support for paging, and the interface. > >> > >> tools/xenpaging is one way to consume that interface. It seems to have suffered from bitrot. > > > > What is the other interface? Thanks! > > Not sure what the question is. There is one interface. What I was referring to, is that tools/xenpaging implements one specific paging policy: victim selection, rate limiting, paging target, all of these are algorithms that entirely define what bang for your money you will get. > Right, but there is other code that uses this interface as well correct? Is it available for users ? From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andres Lagar-Cavilla Subject: Re: Serious issues with xenpaging Date: Fri, 3 Jan 2014 16:17:43 -0500 Message-ID: References: <55E78A57290FB64FA0D3CF672F9F3DA211C793@SJCPEX01CL03.citrite.net> <20131231153330.GC20357@phenom.dumpdata.com> <20131231163110.GA34150@deinos.phlegethon.org> <556C4AC0-F10F-4977-8FCD-3129E416B062@gridcentric.ca> <20140103184154.GA29283@phenom.dumpdata.com> <20140103203139.GA2570@phenom.dumpdata.com> Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20140103203139.GA2570@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Konrad Rzeszutek Wilk Cc: Olaf Hering , Andres Lagar-Cavilla , Tim Deegan , "xen-devel@lists.xen.org" , andres@lagarcavilla.org, "xen-users@lists.xen.org" , Russell Pavlicek List-Id: xen-devel@lists.xenproject.org On Jan 3, 2014, at 3:31 PM, Konrad Rzeszutek Wilk wrote: > On Fri, Jan 03, 2014 at 02:51:14PM -0500, Andres Lagar-Cavilla wrote: >> On Jan 3, 2014, at 1:41 PM, Konrad Rzeszutek Wilk wrote: >> >>> On Fri, Jan 03, 2014 at 09:49:36AM -0500, Andres Lagar-Cavilla wrote: >>>> >>>> On Dec 31, 2013, at 11:31 AM, Tim Deegan wrote: >>>> >>>>> At 10:33 -0500 on 31 Dec (1388482410), Konrad Rzeszutek Wilk wrote: >>>>>> 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 #xenpaging? docs are at SLES manual, rest is mostly this: http://www.gossamer-threads.com/lists/xen/devel/255798 dead feature or usable? >>>>>>> >>>>>>> 22-Dec: @lars_kurth @RCPavlicek Hey guys, I wrote down as much as I could https://piratenpad.de/p/Ik3lOBLniq1L5TEM (since I'm on holiday and not constant online) >>>>>>> >>>>>>> 22-Dec: Yay, tested #xen 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. >>>>> >>>>> Andres really owns this code, so I'll punt to him for an official >>>>> answer, but: >>>> The part actively maintained is the hypervisor support for paging, and the interface. >>>> >>>> tools/xenpaging is one way to consume that interface. It seems to have suffered from bitrot. >>> >>> What is the other interface? Thanks! >> >> Not sure what the question is. There is one interface. What I was referring to, is that tools/xenpaging implements one specific paging policy: victim selection, rate limiting, paging target, all of these are algorithms that entirely define what bang for your money you will get. >> > > Right, but there is other code that uses this interface as well correct? > Is it available for users ? That I know of, Gridcentric's product. It's available as proprietary software for a fee. I am unaware of a sharing user other than Gridcentric. Virtuata was a mem-event user, Gridcentric is, and others have surfaced on the list (Razvan Cocajaru for instance). Andres From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: Serious issues with xenpaging Date: Mon, 6 Jan 2014 19:53:52 +0100 Message-ID: <20140106185352.GB2443@aepfle.de> References: <55E78A57290FB64FA0D3CF672F9F3DA211C793@SJCPEX01CL03.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <55E78A57290FB64FA0D3CF672F9F3DA211C793@SJCPEX01CL03.citrite.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Russell Pavlicek Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On Mon, Dec 23, Russell Pavlicek wrote: > 22-Dec: [S:@:S]lars_kurth [S:@:S]RCPavlicek Hey guys, I wrote down as much as I > could https://piratenpad.de/p/Ik3lOBLniq1L5TEM (since I'm on holiday and not > constant online) > [I've taken the liberty of removing the colorful expletive from the final post] Thanks for that. Quoting the above document: > Docs issues: > Most accessible documentation is from SUSE manual > > written for Xen 4.1/xm toolstack The work was done for SLES11SP2. > xenpaging at least on alpine isn't in $PATH, Yes, its a helper for the toolstack, just like qemu-dm. > actual path /usr/lib/xen/bin/xenpaging is weird Its not because its not supposed to be called manually. > Google turns up the SLES docs, the commit and the "how does one test this" thread > SLES docs don't mention experimental, but mailing list threads etc, do. I did some testing during that time and xenpaging works well enough with SP2 and SP3 and its xend based toolstack. > two years after release it would be a good time to have docs + testing sorted Yes, but that did not happen due to lack of time, resources and lack of integration into libxl. > Looking for sources (last time, at least) doesn't show acticity post-2012 > issues: > incoherent: > > specify a KB "size" of the paging region > > but specify a number of pages to hold back > > Decide for one thing, not two. Actually, let us specify any of it? > I bet the system page size is queryable, so why not KB/MB/GB The current pagesize can be obtained by syscalls. Its up to the toolstack to drive xenpaging, so the actual admin interface should be at this level. The values passed to the helper are an internal detail of the toolstack. > /var/lib/xen/xenpaging Path is a bit weird, too. > Should it rather be /var/lib/xen/paging in line with /var/lib/xen/save ... Thats a minor detail. I decided on a default path, so lets stick with it. > Where's docs how to define it in domU.cfg for XL stack? There are no docs because there is no code and not even a usable proposal how to specify the memory related properties for a domU. What exists today is either populate-on-demand or a fixed amount of memory. There was some discussion about two years ago how paging, sharing, PoD and maybe even tmem could be described in a domU.cfg. Nothing was decided. > Sles docs say domU.cfg for xm stack was: > xenpaging = NUMPAGES > Sles docs basically say for cli use post-domU-creation > xenpaging domID NUM > Actual usage is: > /usr/lib/xen/bin/xenpaging -f /var/lib/xen/xenpaging/freebsd2.page - > d 79 -m 524288 I dont think so. The docs say 'memory=N ; actmem=M' and mem-swap-target to adjust actmem at runtime. Old upstream docs/misc/xenpaging.txt is certainly wrong, simply because no code exists to integrate it into the toolstack. 4.2+ is slightly better. > Q's: > - Obviously, the file name handling when not manually setting it up That did not parse. > - How does one pull an overview of current xenpaging consumers? xenpaging is not called by anything. > - Is the paging file autodiscarded at domU termination? It is supposed to be removed, xenpaging will get an event when the domid disappears. In my testing this part works well. > Testing / doc: > - what happens if someone messes up and overcommits the xenpaging area What does that question mean? Does it mean lack of diskspace in dom0? > - is there any protection against it? > - will it block or crash? The overall OOM handling is not very good. Once a guest starts the full amount of memory for a given domU is required. So if the whole system is in overcommit state and all guests do a restart an OOM situation occurs and some guests will not start anymore due to lack of memory. > Nested paging: > Would be nice to document it's needed. This should be the like line 2 > of the docs actually. What is "nested paging"? > Same goes for a note that it's only for HVM domUs, btw. Thats written down in docs/misc/xenpaging.txt. > Us users don't really use HVM whenever possible, so this is an > relevant info. It's moot to see the cool feature, mess around long > since NODOCS and then find out the one use case you got won't work. > Would be nicer to have s/w workaround for nested page tables if it's > not available. Why? On more modern (basically DDR3-Era) hosts we tend > to be CPU-bound these days and have TONs of Ram. For that I'd rather > use tmem to blink out dup's and have compression fancyness instead of > paging. (if that were tested & documented and known stable ;) If you'd > use xenpaging on a current vm host you'd probably topside it if the > memory is ever really allocated. (think, 128GB ram, 16GB paging, > allocate 16GB ... ouch, and it just makes no sense since RAM and > Raid-1 SSD prices are not much different) It's the 4-core 8GB boxes > and embedded where the paging is a good last resort (methinks) - but > there you don't have nested page tables. xenpaging is not a solution but rather a workaround. It can be used to quickly swapout parts of a running guest to free host memory. Its not predictable what pages a guest will access next, so it comes with a high performance cost (even if the pagefile is in dom0 /dev/shm/). Olaf From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Serious issues with xenpaging Date: Fri, 7 Mar 2014 10:43:39 -0500 Message-ID: <20140307154339.GA10945@phenom.dumpdata.com> References: <55E78A57290FB64FA0D3CF672F9F3DA211C793@SJCPEX01CL03.citrite.net> <20131231153330.GC20357@phenom.dumpdata.com> <20131231163110.GA34150@deinos.phlegethon.org> <556C4AC0-F10F-4977-8FCD-3129E416B062@gridcentric.ca> <20140103184154.GA29283@phenom.dumpdata.com> <20140103203139.GA2570@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andres Lagar-Cavilla Cc: Olaf Hering , Tim Deegan , "xen-devel@lists.xen.org" , andres@lagarcavilla.org, "xen-users@lists.xen.org" , Russell Pavlicek List-Id: xen-devel@lists.xenproject.org On Fri, Jan 03, 2014 at 04:17:43PM -0500, Andres Lagar-Cavilla wrote: > On Jan 3, 2014, at 3:31 PM, Konrad Rzeszutek Wilk wrote: > > > On Fri, Jan 03, 2014 at 02:51:14PM -0500, Andres Lagar-Cavilla wrote: > >> On Jan 3, 2014, at 1:41 PM, Konrad Rzeszutek Wilk wrote: > >> > >>> On Fri, Jan 03, 2014 at 09:49:36AM -0500, Andres Lagar-Cavilla wrote: > >>>> > >>>> On Dec 31, 2013, at 11:31 AM, Tim Deegan wrote: > >>>> > >>>>> At 10:33 -0500 on 31 Dec (1388482410), Konrad Rzeszutek Wilk wrote: > >>>>>> 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 #xenpaging? docs are at SLES manual, rest is mostly this: http://www.gossamer-threads.com/lists/xen/devel/255798 dead feature or usable? > >>>>>>> > >>>>>>> 22-Dec: @lars_kurth @RCPavlicek Hey guys, I wrote down as much as I could https://piratenpad.de/p/Ik3lOBLniq1L5TEM (since I'm on holiday and not constant online) > >>>>>>> > >>>>>>> 22-Dec: Yay, tested #xen 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. > >>>>> > >>>>> Andres really owns this code, so I'll punt to him for an official > >>>>> answer, but: > >>>> The part actively maintained is the hypervisor support for paging, and the interface. > >>>> > >>>> tools/xenpaging is one way to consume that interface. It seems to have suffered from bitrot. > >>> > >>> What is the other interface? Thanks! > >> > >> Not sure what the question is. There is one interface. What I was referring to, is that tools/xenpaging implements one specific paging policy: victim selection, rate limiting, paging target, all of these are algorithms that entirely define what bang for your money you will get. > >> > > > > Right, but there is other code that uses this interface as well correct? > > Is it available for users ? > > That I know of, Gridcentric's product. It's available as proprietary software for a fee. I am unaware of a sharing user other than Gridcentric. Virtuata was a mem-event user, Gridcentric is, and others have surfaced on the list (Razvan Cocajaru for instance). In the context of http://wiki.xenproject.org/wiki/GSoc_2014#Lazy_restore_using_memory_paging should that be removed then? As the dependency of it would be to first 'un-bitrot' it and that might take more than the original GSoC problem statement describes?? > > Andres > From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andres Lagar-Cavilla Subject: Re: Serious issues with xenpaging Date: Fri, 7 Mar 2014 10:47:39 -0500 Message-ID: References: <55E78A57290FB64FA0D3CF672F9F3DA211C793@SJCPEX01CL03.citrite.net> <20131231153330.GC20357@phenom.dumpdata.com> <20131231163110.GA34150@deinos.phlegethon.org> <556C4AC0-F10F-4977-8FCD-3129E416B062@gridcentric.ca> <20140103184154.GA29283@phenom.dumpdata.com> <20140103203139.GA2570@phenom.dumpdata.com> <20140307154339.GA10945@phenom.dumpdata.com> Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20140307154339.GA10945@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Konrad Rzeszutek Wilk Cc: Olaf Hering , Andres Lagar-Cavilla , Tim Deegan , "xen-devel@lists.xen.org" , andres@lagarcavilla.org, "xen-users@lists.xen.org" , Russell Pavlicek List-Id: xen-devel@lists.xenproject.org On Mar 7, 2014, at 10:43 AM, Konrad Rzeszutek Wilk wrote: > On Fri, Jan 03, 2014 at 04:17:43PM -0500, Andres Lagar-Cavilla wrote: >> On Jan 3, 2014, at 3:31 PM, Konrad Rzeszutek Wilk wrote: >> >>> On Fri, Jan 03, 2014 at 02:51:14PM -0500, Andres Lagar-Cavilla wrote: >>>> On Jan 3, 2014, at 1:41 PM, Konrad Rzeszutek Wilk wrote: >>>> >>>>> On Fri, Jan 03, 2014 at 09:49:36AM -0500, Andres Lagar-Cavilla wrote: >>>>>> >>>>>> On Dec 31, 2013, at 11:31 AM, Tim Deegan wrote: >>>>>> >>>>>>> At 10:33 -0500 on 31 Dec (1388482410), Konrad Rzeszutek Wilk wrote: >>>>>>>> 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 #xenpaging? docs are at SLES manual, rest is mostly this: http://www.gossamer-threads.com/lists/xen/devel/255798 dead feature or usable? >>>>>>>>> >>>>>>>>> 22-Dec: @lars_kurth @RCPavlicek Hey guys, I wrote down as much as I could https://piratenpad.de/p/Ik3lOBLniq1L5TEM (since I'm on holiday and not constant online) >>>>>>>>> >>>>>>>>> 22-Dec: Yay, tested #xen 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. >>>>>>> >>>>>>> Andres really owns this code, so I'll punt to him for an official >>>>>>> answer, but: >>>>>> The part actively maintained is the hypervisor support for paging, and the interface. >>>>>> >>>>>> tools/xenpaging is one way to consume that interface. It seems to have suffered from bitrot. >>>>> >>>>> What is the other interface? Thanks! >>>> >>>> Not sure what the question is. There is one interface. What I was referring to, is that tools/xenpaging implements one specific paging policy: victim selection, rate limiting, paging target, all of these are algorithms that entirely define what bang for your money you will get. >>>> >>> >>> Right, but there is other code that uses this interface as well correct? >>> Is it available for users ? >> >> That I know of, Gridcentric's product. It's available as proprietary software for a fee. I am unaware of a sharing user other than Gridcentric. Virtuata was a mem-event user, Gridcentric is, and others have surfaced on the list (Razvan Cocajaru for instance). > > In the context of http://wiki.xenproject.org/wiki/GSoc_2014#Lazy_restore_using_memory_paging > should that be removed then? As the dependency of it would be to first 'un-bitrot' it and that > might take more than the original GSoC problem statement describes?? My take is that whatever xenpaging un-bitroting may be needed, it will be completely independent of the GSOC project. One objective of this GSOC project is to show another way to put men paging to use. I envision this project to be entirely user-space dom0 code, and to not rely on any existing tools/xenpaging code (ok, maybe refactor the set up of the paging event ring). Does that make sense? Thanks Andres > >> >> Andres >> From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: Serious issues with xenpaging Date: Fri, 7 Mar 2014 16:54:09 +0100 Message-ID: <20140307155409.GA10037@aepfle.de> References: <55E78A57290FB64FA0D3CF672F9F3DA211C793@SJCPEX01CL03.citrite.net> <20131231153330.GC20357@phenom.dumpdata.com> <20131231163110.GA34150@deinos.phlegethon.org> <556C4AC0-F10F-4977-8FCD-3129E416B062@gridcentric.ca> <20140103184154.GA29283@phenom.dumpdata.com> <20140103203139.GA2570@phenom.dumpdata.com> <20140307154339.GA10945@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20140307154339.GA10945@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Konrad Rzeszutek Wilk Cc: Andres Lagar-Cavilla , Tim Deegan , "xen-devel@lists.xen.org" , andres@lagarcavilla.org, "xen-users@lists.xen.org" , Russell Pavlicek List-Id: xen-devel@lists.xenproject.org On Fri, Mar 07, Konrad Rzeszutek Wilk wrote: > In the context of http://wiki.xenproject.org/wiki/GSoc_2014#Lazy_restore_using_memory_paging > should that be removed then? As the dependency of it would be to first 'un-bitrot' it and that > might take more than the original GSoC problem statement describes?? While its a good idea, it can HVM only at this point because PV doesnt do paging. So its real work to get this done. Olaf From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andres Lagar-Cavilla Subject: Re: Serious issues with xenpaging Date: Fri, 7 Mar 2014 10:55:59 -0500 Message-ID: References: <55E78A57290FB64FA0D3CF672F9F3DA211C793@SJCPEX01CL03.citrite.net> <20131231153330.GC20357@phenom.dumpdata.com> <20131231163110.GA34150@deinos.phlegethon.org> <556C4AC0-F10F-4977-8FCD-3129E416B062@gridcentric.ca> <20140103184154.GA29283@phenom.dumpdata.com> <20140103203139.GA2570@phenom.dumpdata.com> <20140307154339.GA10945@phenom.dumpdata.com> <20140307155409.GA10037@aepfle.de> Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20140307155409.GA10037@aepfle.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Olaf Hering Cc: Andres Lagar-Cavilla , Tim Deegan , "xen-devel@lists.xen.org" , andres@lagarcavilla.org, "xen-users@lists.xen.org" , Russell Pavlicek List-Id: xen-devel@lists.xenproject.org On Mar 7, 2014, at 10:54 AM, Olaf Hering wrote: > On Fri, Mar 07, Konrad Rzeszutek Wilk wrote: > >> In the context of http://wiki.xenproject.org/wiki/GSoc_2014#Lazy_restore_using_memory_paging >> should that be removed then? As the dependency of it would be to first 'un-bitrot' it and that >> might take more than the original GSoC problem statement describes?? > > While its a good idea, it can HVM only at this point because PV doesnt > do paging. So its real work to get this done. Agreed. And certainly no gimme. But they have a couple months to sink into this. Thanks Andres > > Olaf