[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Active Memory Defragmentation: Our implementation & problems

To: Dave Hansen <haveblue@xxxxxxxxxx>, Alok Mooley <rangdi@xxxxxxxxx>
Subject: Re: Active Memory Defragmentation: Our implementation & problems
From: "Martin J. Bligh" <mbligh@xxxxxxxxxxx>
Date: Tue, 03 Feb 2004 14:26:19 -0800
cc: Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>,linux-mm <linux-mm@xxxxxxxxx>
In-Reply-To: <1075843615.28252.17.camel@nighthawk>
Original-Recipient: rfc822;linux-mm@kvack.org
References: <20040203044651.47686.qmail@web9705.mail.yahoo.com> <1075843615.28252.17.camel@nighthawk>
Sender: Rik van Riel <riel@xxxxxxxxxxxxxxxxxxxx>

> I'll stop there for now.  There seems to be a lot of code in the file
> that's one-off from current kernel code.  I think a close examination of
> currently available kernel functions could drasticly reduce the size of
> your module.  

Preferably to 0 ... this should be part of the core kernel, not a module.

M.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

References:
- Active Memory Defragmentation: Our implementation & problems
  - From: Alok Mooley
- Re: Active Memory Defragmentation: Our implementation & problems
  - From: Dave Hansen

Prev by Date: Re: Active Memory Defragmentation: Our implementation & problems
Next by Date: Re: VM benchmarks
Prev by thread: Re: Active Memory Defragmentation: Our implementation & problems
Next by thread: Re: Active Memory Defragmentation: Our implementation & problems
Index(es):
- Date
- Thread