[lkml]   [2004]   [Feb]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Active Memory Defragmentation: Our implementation & problems
--- "Richard B. Johnson" <> >
If this is an Intel x86 machine, it is impossible
> for pages
> to get fragmented in the first place. The hardware
> allows any
> page, from anywhere in memory, to be concatenated
> into linear
> virtual address space. Even the kernel address space
> is virtual.
> The only time you need physically-adjacent pages is
> if you
> are doing DMA that is more than a page-length at a
> time. The
> kernel keeps a bunch of those pages around for just
> that
> purpose.
> So, if you are making a "memory defragmenter", it is
> a CPU time-sink.
> That's all.

What if the external fragmentation increases so much
that it is not possible to find a large sized block?
Then, is it not better to defragment rather than swap
or fail?


Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:00    [W:0.154 / U:0.188 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site