Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262903AbTFJOEw (ORCPT ); Tue, 10 Jun 2003 10:04:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262878AbTFJODS (ORCPT ); Tue, 10 Jun 2003 10:03:18 -0400 Received: from rsys000a.roke.co.uk ([193.118.201.102]:34063 "HELO rsys000a.roke.co.uk") by vger.kernel.org with SMTP id S262850AbTFJOCh (ORCPT ); Tue, 10 Jun 2003 10:02:37 -0400 From: "ZCane, Ed (Test Purposes)" To: Linux kernel Message-ID: <004901c32f5a$d68b2070$d8c176c1@roke.co.uk> References: Subject: Re: Large files Date: Tue, 10 Jun 2003 15:16:08 +0100 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1351 Lines: 40 Dear All, I'm allocating a large buffer at boot-time, from the kernel, using alloc_bootmem_low_pages, which I wish to use for DMA from an device driver. For example, the bootmem returns an address of 0xc0006000. This all works fine, but... What is the mechanism for communicating this address to user-space processes, and mapping it to a virtual address, so that they can use my buffer? I want user-space processes to be able to read and write from this block of memory, without having to be suid root (if possible). Cheers, Ed begin 666 RMRL-Disclaimer.txt M4F5G:7-T97)E9"!/9F9I8V4Z(%)O:V4@36%N;W(@4F5S96%R8V@@3'1D+"!3 M:65M96YS($AO=7-E+"!/;&1B=7)Y+"!"2!W:71H;W5T('!E