On Tue, May 19, 2015 at 2:46 PM, Mel Gorman wrote:
> On Thu, May 14, 2015 at 04:19:45PM +0200, Anisse Astier wrote:
>> Hi,
>>
>> - it can help with long-term memory consumption in an environment with
>>multiple VMs and Kernel Same-page Merging on the host. [2]
>
> This is not quantified but a
On 19 May 2015 at 13:46, Mel Gorman wrote:
> On Thu, May 14, 2015 at 04:19:45PM +0200, Anisse Astier wrote:
> > Hi,
> >
> > I'm trying revive an old debate here[1], though with a simpler approach than
> > was previously tried. This patch series implements a new option to sanitize
> > freed pages,
On Tue, May 19, 2015 at 02:35:40PM +0100, One Thousand Gnomes wrote:
> > may be some benefits in some cases, I think it's a weak justification for
> > always zeroing pages on free.
>
> There are much better reasons for zero on free, including the improved
> latency when pages are faulted in.
Not
> may be some benefits in some cases, I think it's a weak justification for
> always zeroing pages on free.
There are much better reasons for zero on free, including the improved
latency when pages are faulted in. For virtualisation there are two
interfaces that would probably make more sense
1.
On Thu, May 14, 2015 at 04:19:45PM +0200, Anisse Astier wrote:
> Hi,
>
> I'm trying revive an old debate here[1], though with a simpler approach than
> was previously tried. This patch series implements a new option to sanitize
> freed pages, a (very) small subset of what is done in PaX/grsecurity
Hi,
I'm trying revive an old debate here[1], though with a simpler approach than
was previously tried. This patch series implements a new option to sanitize
freed pages, a (very) small subset of what is done in PaX/grsecurity[3],
inspired by a previous submission [4].
There are a few different us
6 matches
Mail list logo
