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, 17 Nov 2012 00:02:44 -0500 From: Vladislav Bolkhovitin <vst@...b.net> To: 杨苏立 Yang Su Li <suli@...wisc.edu> CC: General Discussion of SQLite Database <sqlite-users@...ite.org>, Theodore Ts'o <tytso@....edu>, Richard Hipp <drh@...ci.com>, linux-kernel <linux-kernel@...r.kernel.org>, linux-fsdevel@...r.kernel.org Subject: Re: [sqlite] light weight write barriers 杨苏立 Yang Su Li, on 11/15/2012 11:14 AM wrote: > 1. fsync actually does two things at the same time: ordering writes (in a > barrier-like manner), and forcing cached writes to disk. This makes it very > difficult to implement fsync efficiently. Exactly! > However, logically they are two distinctive functionalities Exactly! Those two points are exactly why concept of barriers must be forgotten for sake of productivity and be replaced by a finer grained abstractions as well as why they where removed from the Linux kernel Vlad -- 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