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]

Message-ID: <6a89f9d50808060920t168d533g5d440b444e7c09fc@mail.gmail.com>
Date:	Wed, 6 Aug 2008 18:20:40 +0200
From:	"Stephane Marchesin" <marchesin@...s.u-strasbg.fr>
To:	"Keith Packard" <keithp@...thp.com>
Cc:	"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 8/5/08, Keith Packard <keithp@...thp.com> wrote:
> On Mon, 2008-08-04 at 22:25 -0400, John Stoffel wrote:
>
>  > What about the onboard memory of graphics cards?  Isn't that where
>  > Textures and such are stored as well?  So once something is loaded to
>  > the card, shouldn't you be able to free it in system memory?  Or swap
>  > it out ahead of time?
>
>
> Right now, I'm working only on Intel integrated graphics, which doesn't
>  have any on-board memory. My thinking is that we'd best solve the
>  easiest case first before attempting the harder discrete graphics
>  driver. Plus, Intel pays me do do integrated graphics, so I have an
>  incentive.
>

Right, but it sounds adventurous to merge this work upstream before it
is generic enough to work on discrete cards. Right now it only works
on intel integrated cards ; integrated cards are one business,
discrete are a completely different world and the issues afoot
completely different.

Should this go upstream, the kernel guys have to keep in mind and
accept the possibility that another memory manager might be needed at
some point.

Stephane
--
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/