On Sun, Dec 8, 2013 at 10:58 PM, Michael Schmitz
<schm...@biophys.uni-duesseldorf.de> wrote:
>> Amiboot already has memfile support, so you can specify the order of the
>> memory chunks. What's "missing" is a way to specify memory chunk
>> priorities.
>> A naive method is to just assume the first chunk has the highest priority
>> (but you probably don't want that on Atari, where ST-RAM would be the
>> first
>> chunk by default).
>
> It already is (has to be, due to lack of sparse mem support). And the kernel
> lives in ST-RAM pretty much always.
I know it is, but TT-RAM should be faster, right?
>> Alternatively, it could be done automatically, by the kernel measuring
>> read
>> (and/or write) performance of the different memory chunks in a loop
>> similar
>> to the delay loop calibration.
>
> While disabling caches, presumably? How do we do that - map the test chunk
> as nocache?
As long as you read enough data, it should be OK.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAMuHMdVPfsLGWFNU1rN0AxF33eg207iMQ5=6wph9r_zx7_q...@mail.gmail.com
