From 03cbaa5b845979efd943c571339b470b7efd8943 Mon Sep 17 00:00:00 2001 From: InstantGratimification Date: Wed, 3 May 2017 15:00:56 +0000 Subject: [PATCH] Update qmemman.md --- services/qmemman.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/services/qmemman.md b/services/qmemman.md index 499d3bf4..471acb95 100644 --- a/services/qmemman.md +++ b/services/qmemman.md @@ -16,7 +16,7 @@ Rationale Traditionally, Xen VMs are assigned a fixed amount of memory. It is not the optimal solution, as some VMs may require more memory than assigned initially, while others underutilize memory. Thus, there is a need for solution capable of shifting free memory from VM to another VM. -The [tmem](http://oss.oracle.com/projects/tmem/) project provides a "pseudo-RAM" that is assigned on per-need basis. However this solution has some disadvantages: +The [tmem](https://oss.oracle.com/projects/tmem/) project provides a "pseudo-RAM" that is assigned on per-need basis. However this solution has some disadvantages: - It does not provide real RAM, just an interface to copy memory to/from fast, RAM-based storage. It is perfect for swap, good for file cache, but not ideal for many tasks. - It is deeply integrated with the Linux kernel. When Qubes will support Windows guests natively, we would have to port *tmem* to Windows, which may be challenging.