mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ameya Mitragotri" <ameya.mitragotri@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: in-kernel data transfer between devices
Date: Sat, 24 Mar 2007 00:41:00 +0530	[thread overview]
Message-ID: <88df6dda0703231211j509bc95eu5bf51d4c1e8fe24e@mail.gmail.com> (raw)

Hello,
I'm trying to write data from device memory (VRAM in this case) to the
HDD with a kernel module. I want to avoid using the cache so i tried
to do a direct-io. Reading the code i figured it used 'get_user_pages'
and since VRAM is io mapped, those pages are marked VM_IO and hence
directio fails. Why is it taboo to write VM_IO pages using directio?
(is it because Device -> Device DMA is not possible?)

Now attempting to still do the same, im trying to copy VRAM data to a
buffer and still try and use the directio path. it will mean bypassing
the get_user_pages and may mean ugly hacking, but then i also read a
little about splice.  Wondering if splice is the way to go for a
device memory to disk in kernel data transfer?

I'm doing the above as an experiment. My actual goal is to transfer
data between devices in-kernel.

Thanks
Ameya

                 reply	other threads:[~2007-03-23 19:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=88df6dda0703231211j509bc95eu5bf51d4c1e8fe24e@mail.gmail.com \
    --to=ameya.mitragotri@gmail.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®