Searched refs:large (Results 1 – 25 of 31) sorted by relevance
12
| /system/core/fs_mgr/libfiemap/ |
| D | README.md | 6 library works by using `libfiemap_writer` to allocate large files within
18 a large image may have to be split into multiple files. On Ext4 the limit is
58 If an image was too large to store a single file on the underlying filesystem,
|
| /system/nfc/ |
| D | .clang-format | 19 # accommodate for handling of the large legacy code base.
|
| /system/bt/ |
| D | .clang-format | 19 # accommodate for handling of the large legacy code base.
|
| /system/bt/gd/ |
| D | .clang-format | 19 # accommodate for handling of the large legacy code base.
|
| /system/core/fs_mgr/libsnapshot/ |
| D | PowerTest.md | 8 Start by creating two large files that will be used as the pre-merge and post-merge state. You can …
|
| /system/memory/libmemunreachable/tests/ |
| D | Allocator_test.cpp | 87 TEST_F(AllocatorTest, large) { in TEST_F() argument
|
| /system/libhidl/ |
| D | Android.bp | 74 // - large dependency sizes
|
| /system/sepolicy/prebuilts/api/29.0/private/ |
| D | gsid.te | 65 # 1. fallocate a file large enough to hold the signed GSI
|
| /system/sepolicy/private/ |
| D | gsid.te | 90 # 1. fallocate a file large enough to hold the signed GSI
|
| /system/sepolicy/prebuilts/api/30.0/private/ |
| D | gsid.te | 90 # 1. fallocate a file large enough to hold the signed GSI
|
| /system/core/libcutils/ |
| D | trace-dev.inc | 167 ALOGE("Error parsing trace property: Number too large: %s", value);
|
| /system/core/adb/ |
| D | protocol.txt | 75 large maxdata value, the connection with the other side must be closed.
|
| /system/update_engine/ |
| D | update_metadata.proto | 98 // of the block. If a file's data is too large for one block, it overflows
|
| D | README.md | 292 quite large in size. A delta payload, on the other hand, is a differential
485 large and it takes a long time to run all the unit tests. To run all unit tests
|
| /system/update_engine/update_engine/ |
| D | update_metadata.proto | 98 // of the block. If a file's data is too large for one block, it overflows
|
| /system/core/fastboot/ |
| D | README.md | 295 C=1 indicates a continuation packet; the data is too large and will
|
| /system/timezone/output_data/icu_overlay/ |
| D | LICENSE | 226 # A large portion of the dictionary entries
|
| /system/timezone/testing/data/test2/output_data/icu_overlay/ |
| D | LICENSE | 226 # A large portion of the dictionary entries
|
| /system/timezone/testing/data/test1/output_data/icu_overlay/ |
| D | LICENSE | 226 # A large portion of the dictionary entries
|
| /system/timezone/testing/data/test3/output_data/icu_overlay/ |
| D | LICENSE | 226 # A large portion of the dictionary entries
|
| /system/core/fastboot/fuzzy_fastboot/ |
| D | README.md | 363 as running the whole things with a large configuration can take over 30 minutes.
|
| /system/media/audio_utils/ |
| D | Doxyfile.orig | 380 # doxygen will become slower. If the cache is too large, memory is wasted. The
933 # will make the HTML file larger and loading of large files a bit slower, you
1455 # For large projects the javascript based search engine can be slow, then
2261 # or 2 may greatly reduce the computation time needed for large code bases. Also
|
| D | Doxyfile.bak | 380 # doxygen will become slower. If the cache is too large, memory is wasted. The
933 # will make the HTML file larger and loading of large files a bit slower, you
1455 # For large projects the javascript based search engine can be slow, then
2261 # or 2 may greatly reduce the computation time needed for large code bases. Also
|
| /system/chre/chre_api/doc/ |
| D | Doxyfile | 398 # doxygen will become slower. If the cache is too large, memory is wasted. The
974 # will make the HTML file larger and loading of large files a bit slower, you
1500 # For large projects the javascript based search engine can be slow, then
2364 # or 2 may greatly reduce the computation time needed for large code bases. Also
|
| /system/chre/pal/doc/ |
| D | Doxyfile | 398 # doxygen will become slower. If the cache is too large, memory is wasted. The
974 # will make the HTML file larger and loading of large files a bit slower, you
1500 # For large projects the javascript based search engine can be slow, then
2364 # or 2 may greatly reduce the computation time needed for large code bases. Also
|
12