| 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: <1241822238.19600.336.camel@nigel-laptop> Date: Sat, 09 May 2009 08:37:18 +1000 From: Nigel Cunningham <nigel@...onice.net> To: "Rafael J. Wysocki" <rjw@...k.pl> Cc: Bartlomiej Zolnierkiewicz <bzolnier@...il.com>, Pavel Machek <pavel@....cz>, linux-pm@...ts.linux-foundation.org, tuxonice-devel@...ts.tuxonice.net, linux-kernel@...r.kernel.org Subject: Re: [TuxOnIce-devel] [RFC] TuxOnIce Hi. On Fri, 2009-05-08 at 23:03 +0200, Rafael J. Wysocki wrote: > Also, I think we should aim at targets that are possible to achieve. > Namely, > it is clear to me that various parts of TuxOnIce will have to be reviewed and > commented by the memory management people, the file systems people, the > architecture-dependent code maintainers and so on, and it is much easier to > get someone to have a look at a relatively short series of patches doing one > specific thing at a time than to have him review an entire subsystem. Seeking review is why I've posted the code. I'm not sure what file systems people have to review in what I've posted. I guess the memory management part would be the separate saving of LRU pages and the means by which GEM pages are tracked. Re architecture dependent code maintainers: I don't know what they'd have to do. Nothing in arch/ is touched by the patches I posted. Regards, Nigel -- 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