non cached memory for user space DMA

I am trying to write a MAC driver for Arm 11 MPcore in 2.6.23. The DMA'ble memory required is supposed to be non-cached for performance reasons.

A chunk of memory(~ 6MB) is allocated at startup using bigphys area patch. This physical area in the RAM is mmap'd to userspace as follows and thereafter carved into network buffers:

fd = open("/dev/mem", O_RDWR|O_SYNC);
uptr = mmap(0, sz, PROT_READ|PROT_WRITE, MAP_SHARED|MAP_LOCKED,fd, pptr);

Inspite of using the O_SYNC flag the user space mapping is cached and the DMA'd data is not visible. I tried writing up my own mmap and marked the vma non-cached without any results:

size_t size = vma->vm_end - vma->vm_start;
unsigned long offset = vma->vm_pgoff << PAGE_SHIFT;

vma->vm_page_prot = pgprot_noncached(vma->vm_page_prot);
if (remap_pfn_range(vma, vma->vm_start, offset, size, vma->vm_page_prot)) {
return -EAGAIN;
}

I found that the bigphys patch allocated memory from bootmem and bootmem maps the memory as MT_MEMORY. Is there a way I could reduce bootmem allocation at startup (using kernel boot cmd mem=x ?) ?

The idea is to map the rest of the available memory as MT_DEVICE(assuming it removes the BUFFERABLE & CACHEABLE bits while mapping) so that the kernel mapping is also non-cacheable. Hopefully, this will ease the userspace mapping to non-cached as well ?

thanks,
Deb Rupam Banerjee

Webinar
One Click, Universal Protection: Implementing Centralized Security Policies on Linux Systems

As Linux continues to play an ever increasing role in corporate data centers and institutions, ensuring the integrity and protection of these systems must be a priority. With 60% of the world's websites and an increasing share of organization's mission-critical workloads running on Linux, failing to stop malware and other advanced threats on Linux can increasingly impact an organization's reputation and bottom line.

Learn More

Sponsored by Bit9

Webinar
Linux Backup and Recovery Webinar

Most companies incorporate backup procedures for critical data, which can be restored quickly if a loss occurs. However, fewer companies are prepared for catastrophic system failures, in which they lose all data, the entire operating system, applications, settings, patches and more, reducing their system(s) to “bare metal.” After all, before data can be restored to a system, there must be a system to restore it to.

In this one hour webinar, learn how to enhance your existing backup strategies for better disaster recovery preparedness using Storix System Backup Administrator (SBAdmin), a highly flexible bare-metal recovery solution for UNIX and Linux systems.

Learn More

Sponsored by Storix