linux-kernel - Re: [PATCH] Export shmem_file_setup and shmem

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:	Wed, 06 Aug 2008 10:56:49 -0700
From:	Keith Packard <keithp@...thp.com>
To:	Stephane Marchesin <marchesin@...s.u-strasbg.fr>
Cc:	keithp@...thp.com, Arjan van de Ven <arjan@...radead.org>,
	John Stoffel <john@...ffel.org>,
	Hugh Dickins <hugh@...itas.com>,
	Nick Piggin <nickpiggin@...oo.com.au>,
	Christoph Hellwig <hch@...radead.org>,
	Eric Anholt <eric@...olt.net>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Export shmem_file_setup and shmem_getpage for DRM-GEM

On Wed, 2008-08-06 at 19:32 +0200, Stephane Marchesin wrote:

> Right, but the current code will basically force the discrete card
> drivers to implement backing store for all allocations.

Aside from not really forcing discrete card drivers to to anything
(they're welcome to use or not use this stuff as they prefer), I believe
discrete cards will need backing store to support paging objects to disk
and suspend-to-ram operations.

>  Do we want
> this ? Also, for cards that can handle page-based memory allocations,
> there is no way to make use of this feature, do we want this too ?

I don't see how any of the current code directs how future drivers might
work; the user-level interface is reasonably abstract and should allow
all kinds of internal organizations.

Instead of complaining that the current code might not support some
abstract hardware, please build something that does work and we'll see
how to merge that with code for other drivers.

-- 
keith.packard@...el.com

Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)