[gem5-dev] Re: Use of page size and TLBs in the prefetchers

2020-09-08 Thread Gabe Black via gem5-dev
Ok, no problem, that makes sense. Prefetching pages which are only physically contiguous could be counterproductive, and you'd need to know where that boundary is. Would it make sense to add a page size parameter to the prefetcher? It would be a little less automatic, but would avoid the prefetcher

[gem5-dev] Re: Use of page size and TLBs in the prefetchers

2020-09-07 Thread Nikos Nikoleris via gem5-dev
Hi Gabe, I agree with Isaac, some prefetchers use the page size to avoid crossing page boundaries. These are prefetchers operate on the PA space and have no access to the TLB to avoid the extra complexity or because they are far from the core (e.g., L3 prefetcher). Some other prefetchers operate

[gem5-dev] Re: Use of page size and TLBs in the prefetchers

2020-09-07 Thread Isaac Sánchez Barrera via gem5-dev
Hi, I'm not using Ruby, so just talking about classic. Before the code included support for the TLBs, the prefetchers used the page size to detect page-crossing prefetches in order to discard them. Now it uses that to decide if it can do a direct prefetch or it needs to check the TLB for a tr

[gem5-dev] Re: Use of page size and TLBs in the prefetchers

2020-09-07 Thread Gabe Black via gem5-dev
Actually that's not *quite* the end for isa_traits.hh since the system class uses the PageBytes and PageShift internally to allocate physical memory. It's still very close though. Gabe On Mon, Sep 7, 2020 at 1:06 AM Gabe Black wrote: > Hi folks. I've *almost* eliminated use of the getPageBytes