Re: uncached page allocator

["Dave Airlie" <airlied@gmail.com>]

>
> Write-combining access seems the correct thing here, followed by a
> wmb(). Uncached writing would be horrendously slow.
>
> [snip]
> > So after all that I'd like to have some sort of uncached page list I
> > can allocate pages from
>
> This is exactly what Intel's PAT mechanism exists for - just mark the
> desired access type (index) on the pages you've been allocated.
>
> It's documented in the Intel Architecture Software Design manuals, but
> Linux's support is lacking in certain areas [discussions on LKML],
> which a number of developers have been trying to move forward.
>
> Quite a few significant graphics/HPC etc vendors are forced to use it
> without this complete support, so it would be good to get this
> additional impetus involved...

I'm hoping to pick up the PAT cause at some point soon this stuff is
definitely required to get any use out of modern graphics hardware.

It is slightly orthogonal to the issue I mentioned in that I still
have the problem of allocating uncached memory without the flushing
overheads associated with making pages cached/uncached constantly..

Dave.

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