From: Mark Knecht <markknecht@gmail.com>
To: Eric Anholt <eric@anholt.net>
Cc: Jonathan Campbell <jon@nerdgrounds.com>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Vramfs: filesystem driver to utilize extra RAM on VGA devices
Date: Tue, 27 Jan 2009 09:37:32 -0800 [thread overview]
Message-ID: <5bdc1c8b0901270937h27c48290p4fb5233f06593e44@mail.gmail.com> (raw)
In-Reply-To: <1233031451.4851.31.camel@gaiman>
On Mon, Jan 26, 2009 at 8:44 PM, Eric Anholt <eric@anholt.net> wrote:
> On Mon, 2009-01-26 at 18:59 -0800, Mark Knecht wrote:
<SNIP>
>> >
>>
>> Can the GPU use the data placed in your file system? Do you have
>> strong control as to exactly how the data is mapped into VRAM? I'm
>> thinking about parallel processing - Linux puts data there and then
>> the GPU works on it to produce a result which Linux can eventually
>> fetch.
>
> For that you want something like GEM, which is aware of the graphics
> pipeline and the cache management necessary. Wrapping a filesystem
> around it shouldn't be hard, and would be of some use for debugging.
>
> --
> Eric Anholt
Right. I agree. However over time a number of us in the pro-audio area
have thought about using the GPU for things like building complex
reverb convolutions in real-time. Lots of parallelism in the math.
These machines are not typically very graphically intensive and the
VRAM on the cards isn't required but it's there. Somehow being able to
get data in and out of the VRAM using standard file commands, letting
something like GEM do the work, and then getting the data back seems
appealing.
I hope Jonathan keeps up the efforts. Interesting stuff.
- Mark
next prev parent reply other threads:[~2009-01-27 17:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 23:20 Jonathan Campbell
2009-01-26 23:36 ` H. Peter Anvin
2009-01-26 23:50 ` Jonathan Campbell
2009-01-29 17:04 ` Peter W. Morreale
2009-01-29 17:30 ` Jonathan Campbell
2009-01-29 17:38 ` H. Peter Anvin
2009-01-30 3:19 ` Jonathan Campbell
2009-01-30 4:46 ` H. Peter Anvin
2009-01-30 5:20 ` Willy Tarreau
2009-01-30 5:25 ` H. Peter Anvin
2009-01-27 2:59 ` Mark Knecht
2009-01-27 4:44 ` Eric Anholt
2009-01-27 17:37 ` Mark Knecht [this message]
2009-01-27 21:23 ` Eric Anholt
2009-01-28 6:36 ` Jonathan Campbell
2009-01-28 7:05 ` Dave Airlie
2009-01-28 9:03 ` Jonathan Campbell
2009-01-28 9:42 ` Dave Airlie
2009-01-27 5:07 ` Jonathan Campbell
2009-01-27 18:18 ` Mark Knecht
[not found] ` <497F60A3.6020608@nerdgrounds.com>
2009-01-27 20:49 ` Mark Knecht
2009-01-27 21:15 ` Jonathan Campbell
2009-01-28 6:59 ` Trent Piepho
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5bdc1c8b0901270937h27c48290p4fb5233f06593e44@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=eric@anholt.net \
--cc=jon@nerdgrounds.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®