|author||Peter Seebach <email@example.com>||2013-02-16 12:20:59 -0600|
|committer||Peter Seebach <firstname.lastname@example.org>||2013-02-16 19:26:02 -0600|
allow pseudo to force asynchronous behavior
The openembedded build, at least with RPM or SMART, is heavily affected by the cost of calling fsync or fdatasync on package databases all the time. Gosh, wouldn't it be nice if we could suppress that without making dozens of highly intrusive and risky changes into RPM, various database packages, and so on? Yes, yes it would. If only there were a program which could intercept system calls and change their behavior! Enter --enable-force-async. There are now wrappers for fsync, fdatasync, and a few related functions. If --enable-force-async is set, these wrappers instantly return 0, even if PSEUDO_DISABLED is set. And with any luck, bitbake will now perform a bit better. Credit for this insight goes to Richard Purdie. I've reimplemented this to add the configure option, and make the fsync suppression work even when PSEUDO_DISABLED is set.
Diffstat (limited to 'ChangeLog.txt')
1 files changed, 5 insertions, 0 deletions
diff --git a/ChangeLog.txt b/ChangeLog.txt
index ed9e5fa..3dbf183 100644
@@ -1,3 +1,8 @@
+ * (seebs) Add wrapper setting which automatically returns a fixed
+ value from some wrappers. Add fixed-value wrappers for all the
+ *sync() functions. These are all contingent on --enable-force-async.
* (seebs) Add support for in-memory DB. This, plus upcoming
fsync-related changes, are expected to be big enough to justify