linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Steve Case <steve@edt.com>
To: linux-mm@kvack.org
Subject: map_user_kiobuf and 1 Gb (2.4-test8)
Date: Thu, 05 Oct 2000 13:56:09 -0700	[thread overview]
Message-ID: <39DCEAE9.BDEA23BD@edt.com> (raw)

I'm working on a device driver module for our PCI interface cards which
attempts to map user memory for DMA. I was pleased to find the
map_user_kiobuf function and its allies, since this appears to do
exactly what I need. Everything worked fine, until I sent it to a
customer who has a system w/  1 Gb of memory - it locked up real good as
soon as he tried DMA. After making sure we had the same software -
2.4-test8, with the CONFIG_HIGHMEM4G flag set, two pentium IIIs, etc. we
discovered that everything worked if he pulled a DIMM and went to 768M.
The actual amount of memory used by his test remained fairly small.

In the driver I use map_user_iobuf with the user space address, then
cycle through the maplist filling in a scatter-gather list:

/* scatter - gather list */
struct {
    u_int addr;
    u_int size;
} sg;

size=0;
while (size < xfersize)
    {

                 sg.addr =
virt_to_bus(page_address(iobuf.maplist[entrys]));

/* deal with page crossings */

                 if ((u_int)sg.addr & (PAGE_SIZE - 1))
                    thissize = PAGE_SIZE - ((u_int)sg.addr & (PAGE_SIZE
- 1)) ;
                else
                    thissize= PAGE_SIZE;

                if (size + thissize > xfersize)
                        thissize = xfersize - size ;

/* set scatter-gather element size */
                   sg.size = thissize;

                    size += thissize;

    }

The scatter-gather list itself is allocated using kmalloc(); the bus
address is retrieved using virt_to_bus(). We present our card with the
bus address of the scatter-gather list, from which it does DMA to get
the address/size pairs. This works fine for < 1Gb. So, either the
map_user_iobuf function is giving me a bad (unmapped) address, or
kmalloc/virt_to_bus is breaking down at 1Gb.

Are there any obvious gotchas about using kiobuf in systems >= 1 GB?

Thanks,

Steve Case
Engineering Design Team
steve@edt.com


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

             reply	other threads:[~2000-10-05 20:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-05 20:56 Steve Case [this message]
2000-10-11 17:12 ` Stephen Tweedie

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=39DCEAE9.BDEA23BD@edt.com \
    --to=steve@edt.com \
    --cc=linux-mm@kvack.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