| 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
| ||
|
Message-Id: <1248799724.2288.11.camel@localhost> Date: Tue, 28 Jul 2009 18:48:44 +0200 From: Jerome Glisse <glisse@...edesktop.org> To: Thomas Hellström <thomas@...pmail.org> Cc: linux-kernel@...r.kernel.org, dri-devel@...ts.sf.net Subject: ttm_mem_global On Wed, 2009-07-22 at 10:37 +0200, Thomas Hellström wrote: > TTM has a device struct per device and an optional global struct that is > common for all devices and intended to be per subsystem. > > The only subsystem currently having a global structure is the memory > accounting subsystem: > struct ttm_mem_global Thomas i don't think the way we init ttm_mem_global today make it follow the 1 struct ttm_mem_global for everyone. I think it should be initialized and refcounted by device struct. So on first device creation a ttm_mem_global is created and then anytime a new device is created the refcount of ttm_mem_global is increased. This would mean some static global refcount inside ttm_memory.c, maybe there is something similar to singleton in the linux toolbox. Thought ? Idea ? Cheers, Jerome -- 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/
Powered by blists - more mailing lists