public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: sej <trash@aie-etudes.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: DMA transfer with kiobuf, kernel 2.4.21
Date: Wed, 16 Nov 2005 09:35:45 +0100	[thread overview]
Message-ID: <437AEF61.1030704@aie-etudes.com> (raw)
In-Reply-To: <1132077714.2822.36.camel@laptopd505.fenrus.org>

Hi,
thank you for your help.
I will read the DMA documentation. But I need to make DMA on User memory 
space allocated in user space. Because I don't want the kernel to make 
allocation and deallocation during execution for stability.
Best regards.
Sebastien


Arjan van de Ven wrote :

>On Tue, 2005-11-15 at 18:53 +0100, sej wrote:
>  
>
>>>that sounds the wrong approach.. why don't you make your device driver
>>>export an mmap function.. and let the userspace app use that ?
>>>      
>>>
>>I can't because I need to allocate 128MB of memory per PCI card and if I put for example 4 cards, I'll have 512MB in kernel memory, and I think there will be some problem in kernel.
>>    
>>
>
>no there isn't.. there is no rule that memory you allocate for this as
>to be lowmem... at all.
>
>  
>
>>
>>    
>>
>>>transfer->Descript[i].size        = PAGE_SIZE;
>>>transfer->Descript[i].pciaddr    = (ULONG)
>>>virt_to_phys(page_address(iobuf->maplist[idxIobuf]));
>>> 
>>>
>>>      
>>>
>>>you really need to use the PCI DMA mapping api!
>>>      
>>>
>>I have a plx bridge PCI9656 with a DMA controler. So I have to make a 
>>descriptor table with physical address and size.
>>I work in 32 bits address mode, but I don't know which function to call 
>>to get a 36bits address for my controler.
>>    
>>
>
>see the PCI DMA mapping api. the docs for it are in Documentation/
>
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>
>
>  
>


      reply	other threads:[~2005-11-16  8:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-15 17:39 DMA transfer with kiobuf, kernel 2.4.21 sej
2005-11-15 17:49 ` Arjan van de Ven
2005-11-15 17:53   ` sej
2005-11-15 18:01     ` Arjan van de Ven
2005-11-16  8:35       ` sej [this message]

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=437AEF61.1030704@aie-etudes.com \
    --to=trash@aie-etudes.com \
    --cc=arjan@infradead.org \
    --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