Prev: [PATCH] i2o: Remove the dangerous kobj_to_i2o_device macro
Next: [PATCH 1/1] perf archive: Explain how to use the generated tarball
From: Christoph Lameter on 23 Mar 2010 13:40

Reviewed-by: Christoph Lameter <cl(a)linux-foundation.org>


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Andrew Morton on 6 Apr 2010 20:10
On Fri, 2 Apr 2010 17:02:40 +0100
Mel Gorman <mel(a)csn.ul.ie> wrote:

> Fragmentation index is a value that makes sense when an allocation of a
> given size would fail. The index indicates whether an allocation failure is
> due to a lack of memory (values towards 0) or due to external fragmentation
> (value towards 1). For the most part, the huge page size will be the size
> of interest but not necessarily so it is exported on a per-order and per-zone
> basis via /proc/extfrag_index

(/proc/sys/vm?)

Like unusable_index, this seems awfully specialised. Perhaps we could
hide it under CONFIG_MEL, or even put it in debugfs with the intention
of removing it in 6 or 12 months time. Either way, it's hard to
justify permanently adding this stuff to every kernel in the world?


I have a suspicion that all the info in unusable_index and
extfrag_index could be computed from userspace using /proc/kpageflags
(and perhaps a bit of dmesg-diddling to find the zones). If that can't
be done today, I bet it'd be pretty easy to arrange for it.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH] i2o: Remove the dangerous kobj_to_i2o_device macro
Next: [PATCH 1/1] perf archive: Explain how to use the generated tarball