mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Baumann <baumann@kip.uni-heidelberg.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Problem with DMA buffer (in 2.2.15)
Date: Thu, 22 Feb 2001 18:20:42 +0100	[thread overview]
Message-ID: <20010222182042.A9968@kip.uni-heidelberg.de> (raw)
In-Reply-To: <20010222172458.A9717@kip.uni-heidelberg.de> <3A95409D.85E89D95@berlin.de>
In-Reply-To: <3A95409D.85E89D95@berlin.de>; from n.roos@berlin.de on Thu, Feb 22, 2001 at 05:38:53PM +0100

On Thu, Feb 22, 2001 at 05:38:53PM +0100, Norbert Roos wrote:
> Christoph Baumann wrote:
> 
> > is to do this in steps of PAGE_SIZE. What I'm looking for is a kernel routine
> > to force the mapping of previous unmapped pages. Browsing through the source
> > in mm/ I found make_pages_present(). Could this be the solution? I hadn't the
> 
> Have you already looked at mlock(2)?

Well I would have done all this (mlock, alloc buffer in kernel space and map it to user space etc.). But the critical issue is that all should be code compatible to Win (ducking away...). The API under Win allows chain DMA from user space
so the program which was initially developed under Win uses this feature. My
module needs to jump in to support this. Another problem is that the buffer
is often reallocated. 

Christoph

-- 
**********************************************************
* Christoph Baumann                                      *
* Kirchhoff-Institut für Physik - Uni Heidelberg         *
* Mail: baumann@kip.uni-heidelberg.de                    *
* Phone: ++49-6221-54-4329                               *
**********************************************************


  reply	other threads:[~2001-02-22 17:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-22 16:24 Christoph Baumann
2001-02-22 16:38 ` Norbert Roos
2001-02-22 17:20   ` Christoph Baumann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-21 17:12 Christoph Baumann

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=20010222182042.A9968@kip.uni-heidelberg.de \
    --to=baumann@kip.uni-heidelberg.de \
    --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®