HomeSort by relevance Sort by last modified time
    Searched full:ext4 (Results 51 - 75 of 150) sorted by null

1 23 4 5 6

  /external/e2fsprogs/misc/
e2image.8.in 7 e2image \- Save critical ext2/ext3/ext4 filesystem metadata to a file
18 program will save critical ext2, ext3, or ext4 filesystem metadata located on
tune2fs.8.in 7 tune2fs \- adjust tunable filesystem parameters on ext2/ext3/ext4 filesystems
91 parameters on Linux ext2, ext3, or ext4 filesystems. The current values
206 The ext4 file system driver will first apply
451 disabled. (This option is currently only supported by the ext4 file
461 currently only supported by the ext4 file system driver in 2.6.35+
470 purposes. (This option is currently only supported by the ext4 file
476 only supported by the ext4 file system driver in 2.6.35+ kernels.)
556 features are only supported by the ext4 filesystem.
  /external/llvm/test/Transforms/SROA/
big-endian.ll 108 ; CHECK-NEXT: %[[ext4:.*]] = zext i16 1 to i56
109 ; CHECK-NEXT: %[[shift4:.*]] = shl i56 %[[ext4]], 40
  /system/extras/ext4_utils/
contents.c 31 #include "ext4.h"
286 * assert that the elements in the ext4 xattr section are in sorted order
288 * The ext4 filesystem requires extended attributes to be sorted when
289 * they're not stored in the inode. The kernel ext4 code uses the following
301 * the Linux kernel file fs/ext4/xattr.c function ext4_xattr_find_entry().
  /external/e2fsprogs/lib/blkid/
probe.c 305 ret = (fs_proc_check("ext4") || check_for_modules("ext4"));
335 * If the filesystem does not have a journal and ext2 and ext4
348 * filesystem code, but ext4dev is not supported, and ext4 is,
350 * detected as ext4 in that case.
353 * filesystem, then it can only be used by ext4 and NOT by
389 /* Ext4 has at least one feature which ext3 doesn't understand */
399 * filesystem code, and ext4dev is supported or ext4 is not
400 * supported, then don't call ourselves ext4, so we can redo
404 * filesystem, then it can only be used by ext4 and NOT b
    [all...]
  /build/target/board/generic/
BoardConfig.mk 74 BOARD_CACHEIMAGE_FILE_SYSTEM_TYPE := ext4
  /cts/tests/tests/security/src/android/security/cts/
KernelSettingsTest.java 119 * Verify that ext4 extended attributes (xattrs) are enabled in the
  /device/lge/hammerhead/
BoardConfig.mk 81 BOARD_CACHEIMAGE_FILE_SYSTEM_TYPE := ext4
  /external/chromium/chrome/common/
important_file_writer.h 37 // If you want to know more about this approach and ext3/ext4 fsync issues, see
  /external/chromium_org/base/files/
important_file_writer.h 37 // If you want to know more about this approach and ext3/ext4 fsync issues, see
  /device/samsung/manta/
init.manta.rc 66 mount ext4 /dev/block/platform/dw_mmc.0/by-name/efs /factory rw remount
84 mount ext4 /dev/block/platform/dw_mmc.0/by-name/efs /factory ro remount
  /external/chromium_org/components/autofill/core/browser/
phone_field_unittest.cc 115 list_.push_back(new AutofillField(field, ASCIIToUTF16("ext4")));
131 field_type_map_.find(ASCIIToUTF16("ext4")) == field_type_map_.end());
  /external/chromium_org/third_party/leveldatabase/src/doc/
benchmark.html 88 <p>Benchmarks were all performed on a six-core Intel(R) Xeon(R) CPU X5650 @ 2.67GHz, with 12288 KB of total L3 cache and 12 GB of DDR3 RAM at 1333 MHz. (Note that LevelDB uses at most two CPUs since the benchmarks are single threaded: one to run the benchmark, and one for background compactions.) We ran the benchmarks on two machines (with identical processors), one with an Ext3 file system and one with an Ext4 file system. The machine with the Ext3 file system has a SATA Hitachi HDS721050CLA362 hard drive. The machine with the Ext4 file system has a SATA Samsung HD502HJ hard drive. Both hard drives spin at 7200 RPM and have hard drive write-caching enabled (using `hdparm -W 1 [device]`). The numbers reported below are the median of three measurements.</p>
275 <p>Also see the <code>ext4</code> performance numbers below
277 on <code>ext3</code> and <code>ext4</code>.</p>
453 <h2>Note about Ext4 Filesystems</h2>
454 <p>The preceding numbers are for an ext3 file system. Synchronous writes are much slower under <a href="http://en.wikipedia.org/wiki/Ext4">ext4</a> (LevelDB drops to ~31 writes / second and TreeDB drops to ~5 writes / second; SQLite3's synchronous writes do not noticeably drop) due to ext4's different handling of <span class="code">fsync</span> / <span class="code">msync</span> calls. Even LevelDB's asynchronous write performance drops somewhat since it spreads its storage across multiple files and issues <span class="code">fsync</span> calls when switching to a new file.</p>
  /external/e2fsprogs/e2fsck/
e2fsck.conf.5.in 14 while it is checking ext2, ext3, or ext4 filesystems.
130 the test_fs flag if the ext4 filesystem is available on the system. It
  /external/e2fsprogs/lib/ext2fs/
ext2_err.et.in 66 "Wrong magic number for ext4 extent handle"
336 "Wrong magic number for ext4 extent saved path"
  /external/llvm/test/CodeGen/SystemZ/
fp-conv-02.ll 101 %ext4 = fpext float %val4 to double
137 store volatile double %ext4, double *%ptr1
fp-conv-03.ll 119 %ext4 = fpext float %val4 to fp128
155 store volatile fp128 %ext4, fp128 *%ptr1
fp-conv-04.ll 119 %ext4 = fpext double %val4 to fp128
155 store volatile fp128 %ext4, fp128 *%ptr1
int-add-03.ll 161 %ext4 = sext i32 %frob4 to i64
172 %add4 = add i64 %add3, %ext4
int-add-04.ll 161 %ext4 = zext i32 %frob4 to i64
172 %add4 = add i64 %add3, %ext4
int-conv-09.ll 133 %ext4 = sext i32 %val4 to i64
167 store volatile i64 %ext4, i64 *%ptr1
int-conv-10.ll 142 %ext4 = zext i32 %val4 to i64
176 store volatile i64 %ext4, i64 *%ptr1
int-mul-03.ll 161 %ext4 = sext i32 %frob4 to i64
172 %mul4 = mul i64 %mul3, %ext4
int-sub-02.ll 161 %ext4 = sext i32 %frob4 to i64
172 %sub4 = sub i64 %sub3, %ext4
int-sub-03.ll 161 %ext4 = zext i32 %frob4 to i64
172 %sub4 = sub i64 %sub3, %ext4

Completed in 469 milliseconds

1 23 4 5 6