Re: Hugepages demand paging V2 [0/8]: Discussion and overview

[Christoph Lameter]

On Tue, 26 Oct 2004, Robin Holt wrote:

> Sorry for being a stickler here, but the BTE is really part of the
> I/O Interface portion of the shub.  That portion has a seperate clock
> frequency from the memory controller (unfortunately slower).  The BTE
> can zero at a slightly slower speed than the processor.  It does, as
> you pointed out, not trash the CPU cache.
>
> One other feature of the BTE is it can operate asynchronously from
> the cpu.  This could be used to, during a clock interrupt, schedule
> additional huge page zero filling on multiple nodes at the same time.
> This could result in a huge speed boost on machines that have multiple
> memory only nodes.  That has not been tested thoroughly.  We have done
> considerable testing of the page zero functionality as well as the
> error handling.

If the huge patch would support some way of redirecting the clearing of a
huge page then we could:

1. set the huge pte to not present so that we get a fault on access
2. run the bte clearer.
3. On receiving a huge fault we could check for the bte being finished.

This would parallelize the clearing of huge pages. But is that really more
efficient? There may be complexity involved in allowing the clearing of
multiple pages and tracking of the clear in progress is additional
overhead.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/