| 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: <CAB_f4-VG6qke8Lo0kMatjng2vvBitv8Z+xc8TSGndjMf58Qheg@mail.gmail.com> Date: Mon, 18 May 2015 15:01:06 -0400 From: Bill Speirs <bill.speirs@...il.com> To: linux-kernel@...r.kernel.org Subject: Userspace Block Device My goal is to provide Amazon S3 or Google Cloud Storage as a block device. I would like to leverage the libraries that exist for both systems by servicing requests via a user space program. I found 2 LKML threads that talk about a "userspace block device": 2005-11-09: http://article.gmane.org/gmane.linux.kernel/346883 2009-07-27: http://article.gmane.org/gmane.linux.kernel/869784 The first thread resulted in Michael Clark suggesting his kernel module: https://github.com/michaeljclark/userblk The second essentially resulted in "use nbd". Mr. Clark's module is now over 10 years old, and ndb seems like a bit of a Rube Goldberg solution. Does the kernel now supports a facility to service bio requests via user space? If not, what would be the best approach to take? Update Mr. Clark's code? Or is there a newer and more efficient facility for kernel <-> user space communication and transferring of data? Thanks... Bill- -- 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