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]

Date:	Fri, 26 Jun 2009 08:38:36 +0100 (IST)
From:	Dave Airlie <airlied@...ux.ie>
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

> 
> I think it's better to fix userspace to not allocate as much buffer per
> frame as it does now rather than having a pool of wb pages, i removed
> it because on my 64M box memory is getting tight, we need to compute
> the number of page we still based on memory. Also i think it's ok
> to assume that page allocation is fast enough.

Yup we could try decreasing the DMA buffer size, I think the DMA buffer 
would be a lot better suited to suballocation, doing individual bo allocs 
like the code used to was a major hit, assuming page alloc is fast enough 
isn't valid since I've already proved it was a major CPU user when I fixed 
it the first time :)

The problem with making the dma buffer smaller is the having a buffer 
mapped and sent to the kernel for relocs.

Dave.
--
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/