linux-kernel - Re: TTM page pool allocator

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4A439D7D.9030401@shipmail.org>
Date:	Thu, 25 Jun 2009 17:53:33 +0200
From:	Thomas Hellström <thomas@...pmail.org>
To:	Jerome Glisse <glisse@...edesktop.org>
CC:	Dave Airlie <airlied@...il.com>, linux-kernel@...r.kernel.org,
	dri-devel@...ts.sf.net
Subject: Re: TTM page pool allocator

Jerome Glisse skrev:
> Hi,
>
> Thomas i attach a reworked page pool allocator based on Dave works,
> this one should be ok with ttm cache status tracking. It definitely
> helps on AGP system, now the bottleneck is in mesa vertex's dma
> allocation.
>
> Cheers,
> Jerome
>   
Hi, Jerome!
In general it looks very good. Some things that need fixing:

1)  We must have a way to hand back pages. I still not quite understand 
how the shrink callbacks work and whether they are applicable. Another 
scheme would be to free, say 1MB when we have at least 2MB available.

2) We should avoid including AGP headers if AGP is not configured. 
Either reimplement unmap_page_from_agp or map_page_into_agp or move them 
out from the AGP headers. We've hade complaints before from people with 
AGP free systems that the code doesn't compile.

3) Since we're allocating (and freeing) in batches we should use the 
set_pages_array() interface to avoid a global tlb flush per page.

4) We could now skip the ttm_tt_populate() in ttm_tt_set_caching, since 
it will always allocate cached pages and then transition them.

5) Use TTM_PFX in printouts.

/Thomas

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