Re: Creating 16 MB super-sections for MMIO
Date: Wed Dec 03 2014 - 09:20:19 EST
On 03/12/2014 11:32, Catalin Marinas wrote:
The reasons behind this proposal aren't clear. Are you trying
to optimise mmio register accesses by avoiding TLB misses?
I am trying to minimize TLB "pollution" by using a "huge" page.
The ARM manual states: "Support for Supersections, Sections and
Large pages enables a large region of memory to be mapped using
only a single entry in the TLB."
Is it correct that, if I create a virtual-to-physical mapping of
an 8 MB memory region, then, in the best-case scenario, the kernel
will create 8 Sections? Thus my mapping would use up to 8 entries
in the TLB at any given time.
Instead, if I create a V2P mapping of a 16 MB region, and if the
kernel supports so-called Super-sections, then the mapping would
use only a single entry in the TLB. Right?
Thus creating a Super-section leaves more TLB entries available
for user-space processes and kernel threads, which can only
improve system performance, AFAIU.
On my SoC, physical addresses 0 to 2^24 are reserved for device
memory-mapped registers. There are holes in the region (meaning
addresses that don't map to any register) but the bus is defined
in such a way that
- writing to a hole is a NOP,
-reading from a hole returns 0.
So I'd like to map
physical addresses 0-2^24
virtual addresses 0xf000_0000 - 0xf100_0000
using a Super-section.
And I was hoping that calling iotable_init with a struct map_desc
entry where length = SZ_16M would create such a super-section.
Did that make sense?
As far as I could tell, Linux does not create a super-section in the
case outlined above. Perhaps I misread the source code?
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/