| 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: <AANLkTini5XkSFjwOt55b8VG7aTWqT2tDU8ckGtE9DkN_@mail.gmail.com> Date: Tue, 14 Dec 2010 15:15:00 -0800 From: Tony Luck <tony.luck@...el.com> To: Marco Stornelli <marco.stornelli@...il.com> Cc: Linux Kernel <linux-kernel@...r.kernel.org> Subject: Re: [RFC] persistent store (version 3) (part 1 of 2) On Tue, Dec 14, 2010 at 9:49 AM, Marco Stornelli <marco.stornelli@...il.com> wrote: > Yeah, maybe it wasn't really ready for mainline :) However the idea > behind it, it was the same more or less, to have a piece of memory to > write some persistent information. I dug back into old linux-next trees and found the code in the November editions. You are right - this does look very similar to what I have done. I think my code may be more adaptable to other platforms as I tried hard to separate out the generic part that implements the file system view from the platform driver that peeks and pokes at the hardware to access the persistent memory. It is also accessible to user space without any custom tools. The dream/pmem.c code might do a better job at handling larger amounts of persistent memory than my code, but it looks like it needs some special user tools that use the ioctl(... PMEM_*, ...) operations to set things up. -Tony -- 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