| 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
| ||
|
Date: Sat, 9 May 2009 21:32:10 +0200 From: "Rafael J. Wysocki" <rjw@...k.pl> To: Pavel Machek <pavel@....cz> Cc: nigel@...onice.net, linux-pm@...ts.linux-foundation.org, tuxonice-devel@...ts.tuxonice.net, linux-kernel@...r.kernel.org Subject: Re: [TuxOnIce-devel] [RFC] TuxOnIce On Saturday 09 May 2009, Pavel Machek wrote: > Hi! > > > > And we have different ideas about how things should be done. Userspace > > > vs kernel space. Providing tuning knobs vs not. And so on. > > > > This isn't _that_ important. Actually, I'm not against an entirely in-kernel > > solution, as there are some clear benefits of doing it this way. We only > > need to be careful enough not to break the existing setups. > > Would you elaborate? One benefit is that we need not anything in the initrd for hibernation to work. Another one is that we can get superior performance, for obvious reasons (less copying of data, faster I/O). Yet another is simpler configuration and no need to maintain a separate set of user space tools. I probably could find more. > I would really hate to put progressbar painting into kernel; and if > that's in userspace, we can do compression/encryption there too as > well.... That's correct, we can. But since we have LZO in the kernel now, we can use it for compression just as well, can't we? Thanks, Rafael -- 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