mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: William Waddington <csbwaddington@att.net>
To: linux-kernel@vger.kernel.org
Subject: Re: query regarding 'map_user_kiobuf'
Date: Wed, 30 May 2001 08:12:17 -0700	[thread overview]
Message-ID: <593aht81ed3p199mr0l1m896d32bgr6qnv@4ax.com> (raw)
In-Reply-To: <fa.f4liqpv.6lq2r7@ifi.uio.no> <CA256A5B.00548719.00@d73mta01.au.ibm.com> <fa.e3ea6bv.t0ceia@ifi.uio.no>
In-Reply-To: <fa.e3ea6bv.t0ceia@ifi.uio.no>

On Tue, 29 May 2001 19:30:06 GMT, in fa.linux.kernel you wrote:

>
>mdaljeet@in.ibm.com said:
>> After using the 'map_user_kiobuf', I observed the followiing:
>> 
>> 1. 'kiobuf->maplist[0]->virtual' contains a different virtual address than
>> the user space buffer address
>> 2. But these two addresses are mapped as when i write something using the
>> address 'kiobuf->maplist[0]->virtual' inside the kernel, I see the same
>> data in the user space buffer in my application.
>> 3. I use the 'virt_to_phys' operation to the virtual address
>> 'kiobuf->maplist[0]->virtual' to get the physical address.
>> 4. I use this physical address for DMA operations.
>> 
>> Now, using this information I do a DMA from card to system memory. What I
>> have noticed is that DMA happens somewhere else in the system memory. I am
>> not able to execute most of the commands (ls, chmod, cat, clear etc) after
>> my user program exits.
>> 
>> Am I doing the steps 3 and 4 above right?
>
>After calling map_user_kiobuf(), I believe you should be locking the pages
>in memory by calling lock_kiovec(). Otherwise, nothing prevents them from 
>being paged out again.
>
>Also, the pages may be in high memory and not directly accessible. You should
>use kmap() before touching them from the kernel rather than just using 
>page->virtual, and obviously kunmap() afterwards.
>
>The PCI DMA interface is more complex than simply using virt_to_phys() too, 
>if you want to deal correctly with the highmem case. I'm sure others will 
>give you the details or pointers to the documentation.


David,

I have a couple of user DMA drivers up and running, but in light of your
comment, I am not so sure.

I see the following  w/map_user_kiobuf() in memory.c (2.4.4)

...

/*
 * Force in an entire range of pages from the current process's user VA,
 * and pin them in physical memory.  
 */
 
#define dprintk(x...)
 int map_user_kiobuf(int rw, struct kiobuf *iobuf, unsigned long va, size_t
len)

...

What is the difference between pinning and locking?  I had the impression
that locking had more to do with ownership.

Thanks,
Bill

---------------------------------------
Bill Waddington
Bainbridge Island, WA, USA
csbwaddington@att.net
ikoncorp@att.net
---------------------------------------

  parent reply	other threads:[~2001-05-30 15:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.f4liqpv.6lq2r7@ifi.uio.no>
2001-05-29 14:04 ` mdaljeet
2001-05-29 19:28   ` David Woodhouse
     [not found]   ` <fa.e3ea6bv.t0ceia@ifi.uio.no>
2001-05-30 15:12     ` William Waddington [this message]
2001-05-30 15:37     ` David Woodhouse

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=593aht81ed3p199mr0l1m896d32bgr6qnv@4ax.com \
    --to=csbwaddington@att.net \
    --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®