Searched defs:fdatasync (Results 1 - 8 of 8) sorted by relevance
| /external/chromium_org/third_party/leveldatabase/src/port/ |
| H A D | port_posix.h | 67 // Use fsync() on platforms without fdatasync()
68 #define fdatasync fsync macro
72 // fdatasync() was only introduced in API level 9 on Android. Use fsync()
74 #define fdatasync fsync macro
|
| /external/bison/darwin-lib/ |
| H A D | unistd.h | 844 <http://pubs.opengroup.org/onlinepubs/9699919799/functions/fdatasync.html>. */
846 _GL_FUNCDECL_SYS (fdatasync, int, (int fd));
848 _GL_CXXALIAS_SYS (fdatasync, int, (int fd));
849 _GL_CXXALIASWARN (fdatasync);
851 # undef fdatasync macro
853 _GL_WARN_ON_USE (fdatasync, "fdatasync is unportable - "
854 "use gnulib module fdatasync for portability");
|
| /external/bison/linux-lib/ |
| H A D | unistd.h | 844 <http://pubs.opengroup.org/onlinepubs/9699919799/functions/fdatasync.html>. */
846 _GL_FUNCDECL_SYS (fdatasync, int, (int fd));
848 _GL_CXXALIAS_SYS (fdatasync, int, (int fd));
849 _GL_CXXALIASWARN (fdatasync);
851 # undef fdatasync macro
853 _GL_WARN_ON_USE (fdatasync, "fdatasync is unportable - "
854 "use gnulib module fdatasync for portability");
|
| /external/chromium_org/third_party/leveldatabase/ |
| H A D | env_chromium.cc | 68 int fdatasync(int fildes) { function in namespace:leveldb_env::__anon11244
513 if (fdatasync(fileno(file_)) && !error)
|
| /external/chromium_org/third_party/sqlite/src/src/ |
| H A D | os_unix.c | 3120 ** We do not trust systems to provide a working fdatasync(). Some do.
3122 ** If you know that your system does support fdatasync() correctly,
3123 ** then simply compile with -Dfdatasync=fdatasync
3125 #if !defined(fdatasync) && !defined(__linux__)
3126 # define fdatasync fsync macro
3156 ** Ted Ts'o tells us that fdatasync() will also write the inode if the
3157 ** file size has changed. The only real difference between fdatasync()
3158 ** and fsync(), Ted tells us, is that fdatasync() will not flush the
3161 ** as far as SQLite is concerned, an fdatasync() is always adequate.
3162 ** So, we always use fdatasync() i
[all...] |
| /external/chromium_org/third_party/sqlite/amalgamation/ |
| H A D | sqlite3.c | 27276 ** We do not trust systems to provide a working fdatasync(). Some do.
27278 ** If you know that your system does support fdatasync() correctly,
27279 ** then simply compile with -Dfdatasync=fdatasync
27281 #if !defined(fdatasync) && !defined(__linux__)
27282 # define fdatasync fsync macro
27312 ** Ted Ts'o tells us that fdatasync() will also write the inode if the
27313 ** file size has changed. The only real difference between fdatasync()
27314 ** and fsync(), Ted tells us, is that fdatasync() will not flush the
27317 ** as far as SQLite is concerned, an fdatasync() is always adequate.
27318 ** So, we always use fdatasync() i
[all...] |
| /external/sqlite/dist/orig/ |
| H A D | sqlite3.c | 28213 # define fdatasync macro
[all...] |
| /external/sqlite/dist/ |
| H A D | sqlite3.c | 28231 # define fdatasync macro
[all...] |
Completed in 568 milliseconds