| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <451BDFF3.4040003@saville.com> Date: Thu, 28 Sep 2006 07:45:07 -0700 From: Wink Saville <wink@...ille.com> To: Stephen Hemminger <shemminger@...l.org>, linux-kernel@...r.kernel.org Subject: Re: Zero copy between ISR, kernel and User Stephen Hemminger wrote: > On Tue, 26 Sep 2006 21:01:45 -0700 > Wink Saville <wink@...ille.com> wrote: > > >> Hello, >> >> I would like to allow the transferring of data between ISR's, kernel and >> user code, without requiring copying. I envision allocating buffers in >> the kernel and then mapping them so that they appear at the same >> addresses to all code, and never being swapped out of memory. >> >> Is this feasible for all supported Linux architectures and is there >> existing code that someone could point me towards? >> >> Regards, >> >> Wink Saville >> >> > > Your better off having application mmap a device, then transfer > the data to there. Something like AF_PACKET. > > Is there some reason a kernel module can't mmap first, for instance I assume display drivers might do that? One of the reasons I need it to done in the kernel first is that data could come from the device or other entities before the application is running. But I will study AF_PACKET handling. Thanks, Wink - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists