Home
last modified time | relevance | path

Searched full:ram (Results 1 – 25 of 879) sorted by relevance

12345678910>>...36

/third_party/mbedtls/configs/
Dconfig-suite-b.h27 * - optimized for low RAM usage
76 /* Save RAM at the expense of ROM */
79 /* Save RAM by adjusting to our exact needs */
82 /* Save RAM at the expense of speed, see ecp.h */
96 /* Save ROM and a few bytes of RAM by specifying our own ciphersuite list */
102 * Save RAM at the expense of interoperability: do this only if you control
Dconfig-ccm-psk-tls1_2.h27 * and low RAM usage.
60 * save ROM and a few bytes of RAM by specifying our own ciphersuite list
67 * Save RAM at the expense of interoperability: do this only if you control
74 /* Save RAM at the expense of ROM */
77 /* Save some RAM by adjusting to your exact needs */
Dconfig-ccm-psk-dtls1_2.h27 * and low RAM usage.
69 * save ROM and a few bytes of RAM by specifying our own ciphersuite list
76 * Save RAM at the expense of interoperability: do this only if you control
83 /* Save RAM at the expense of ROM */
86 /* Save some RAM by adjusting to your exact needs */
Dconfig_rsa_aes_cbc.h59 /* Save RAM at the expense of ROM */
62 /* Save RAM by adjusting to our exact needs */
72 /* Save ROM and a few bytes of RAM by specifying our own ciphersuite list */
79 * Save RAM at the expense of interoperability: do this only if you control
Dconfig-thread.h76 /* Save RAM at the expense of ROM */
79 /* Save RAM by adjusting to our exact needs */
82 /* Save ROM and a few bytes of RAM by specifying our own ciphersuite list */
/third_party/rust/rust/tests/run-make/thumb-none-qemu/example/
Dmemory.x8 /* FLASH and RAM are mandatory memory regions */
11 RAM : ORIGIN = 0x20000000, LENGTH = 64K
13 /* More memory regions can declared: for example this is a second RAM region */
18 By default it will be placed at the end of the RAM region */
/third_party/ltp/testcases/kernel/kvm/
Dlib_host.c70 if (!inst->ram[i].userspace_addr) in tst_kvm_find_phys_memslot()
73 base = inst->ram[i].guest_phys_addr; in tst_kvm_find_phys_memslot()
75 if (paddr >= base && paddr - base < inst->ram[i].memory_size) in tst_kvm_find_phys_memslot()
107 ret = (char *)(uintptr_t)inst->ram[slot].userspace_addr; in tst_kvm_get_memptr()
108 return ret + (addr - inst->ram[slot].guest_phys_addr); in tst_kvm_get_memptr()
149 inst->ram[slot] = memslot; in tst_kvm_alloc_memory()
201 tst_res(TWARN, "RAM size increased to %zu bytes", ram_size); in tst_kvm_create_instance()
206 tst_res(TWARN, "RAM size truncated to %zu bytes", ram_size); in tst_kvm_create_instance()
290 memset(inst->ram, 0, sizeof(inst->ram)); in tst_kvm_destroy_instance()
/third_party/lzma/DOC/
Dlzma.txt72 When to use: RAM->RAM decompressing
189 For example, you can use Large RAM Pages (2 MB) in allocBig allocator for
191 Large RAM Pages.
266 Single-call RAM->RAM Compression
269 Single-call RAM->RAM Compression is similar to Compression with callbacks,
Dlzma-specification.txt135 The RAM usage
138 The RAM usage for LZMA decoder is determined by the following parts:
145 The RAM usage for Sliding Window
150 1) The decoding of full stream to one RAM buffer.
152 If we decode full LZMA stream to one output buffer in RAM, the decoder
164 output RAM buffer can require some minor changes in code.
167 The RAM usage for the probability model counters
177 model counters, the RAM usage required by probability model counter arrays
180 RAM = 4 KiB + 1.5 KiB * (1 << (lp + lc))
182 For example, for default LZMA parameters (lp = 0 and lc = 3), the RAM usage is
[all …]
/third_party/rust/crates/nix/src/sys/
Dsysinfo.rs55 /// Returns the total amount of installed RAM in Bytes.
60 /// Returns the amount of completely unused RAM in Bytes.
62 /// "Unused" in this context means that the RAM in neither actively used by
64 /// "wasted" RAM since it currently serves no purpose.
/third_party/lwip/src/core/
Dmem.c337 /** index (-> ram[next]) of the next struct */
339 /** index (-> ram[prev]) of the previous struct */
351 * larger values could prevent too small blocks to fragment the RAM too much. */
370 /** pointer to the heap (ram_heap): for alignment, ram is now a pointer instead of an array */
371 static u8_t *ram; variable
440 return (struct mem *)(void *)&ram[ptr]; in ptr_to_mem()
446 return (mem_size_t)((u8_t *)mem - ram); in mem_to_ptr()
466 LWIP_ASSERT("plug_holes: mem >= ram", (u8_t *)mem >= ram); in plug_holes()
475 /* if mem->next is unused and not end of ram, combine mem and mem->next */ in plug_holes()
511 ram = (u8_t *)LWIP_MEM_ALIGN(LWIP_RAM_HEAP_POINTER); in mem_init()
[all …]
/third_party/jerryscript/targets/esp8266/
Dreadme.md61 ### 6. Optimizing initial RAM usage (ESP8266 specific)
63 the same limited RAM where our code needs to run.
65 …ble to force the compiler to store a constant into ROM and also read it from there thus saving RAM.
/third_party/mesa3d/src/gallium/drivers/r300/
Dr300_chipset.h20 * in the ZMASK RAM, so there is always 16 tiles per one dword. */
37 /* Some chipsets do not have HiZ RAM - other have varying amounts. */
39 /* Some chipsets have zmask ram per pipe some don't. */
/third_party/lwip/
Dbundle.json3 …s lwIP suitable for use in embedded systems with tens of kilobytes of free RAM and room for around…
26 "ram": "", string
/third_party/lzma/
DREADME.md248 1. When to use: RAM->RAM decompressing
378 … can use Large RAM Pages (2 MB) in allocBig allocator for better compression speed. Note that Wind…
466 #### ***Single-call RAM->RAM Compression***
468 Single-call RAM->RAM Compression is similar to Compression with callbacks,
DREADME_zh.md210 1. 使用场景: RAM->RAM decompressing
426 #### ***单次调用 RAM->RAM 压缩***
428 单次调用,RAM->RAM 压缩与设置回调的方式压缩类似, 但你需要提供指向buffers的指针而不是指向回调函数的指针。
/third_party/mbedtls/configs/ext/
Dtfm_mbedcrypto_config_profile_medium.h105 * Comment this macro to generate AES tables in RAM at runtime.
107 * Tradeoff: Using precomputed ROM tables reduces RAM usage by ~8kb
112 * performance if ROM access is slower than RAM access.
122 * Use less ROM/RAM for AES tables.
125 * ROM / RAM (depending on the value of \c MBEDTLS_AES_ROM_TABLES)
129 * Tradeoff: Uncommenting this reduces the RAM / ROM footprint
523 * - p256-m has a much smaller code size and RAM footprint.
/third_party/littlefs/bd/
Dlfs_rambd.h2 * Block device emulated in RAM
54 // Create a RAM block device
/third_party/lwip/contrib/examples/httpd/examples_fs/
Dindex.html29 the RAM usage while still having a full scale TCP. This
31 of kilobytes of free RAM and room for around 40 kilobytes
/third_party/skia/third_party/externals/swiftshader/third_party/llvm-10.0/llvm/lib/Target/AVR/MCTargetDesc/
DAVRTargetStreamer.cpp31 // FIXME: We can disable __do_copy_data if there are no static RAM variables. in finish()
34 OS.emitRawComment("copy all variables from program memory to RAM on startup"); in finish()
/third_party/lwip/src/apps/http/fs/
Dindex.html29 the RAM usage while still having a full scale TCP. This
31 of kilobytes of free RAM and room for around 40 kilobytes
/third_party/openssl/doc/man7/
DEVP_KDF-SCRYPT.pod14 that it deliberately requires a significant amount of RAM for efficient
23 greater than zero. The amount of RAM that scrypt requires for its computation
32 they default to 1048576, 8, and 1, respectively. The maximum amount of RAM that
/third_party/openssl/doc/man3/
DEVP_PKEY_CTX_set_scrypt_N.pod40 EVP_PKEY_CTX_set_scrypt_maxmem_bytes() sets how much RAM key
42 If RAM is exceeded because the load factors are chosen too high, the
/third_party/mesa3d/src/gallium/frontends/nine/
Dnine_memory_helper.c7 * Memory util function to allocate RAM backing for textures.
9 * MANAGED textures have a RAM backing and upload the content to a GPU texture for use
10 * SYSTEMMEM textures are stored in RAM and are meant to be uploaded to DEFAULT textures.
13 * Once the GPU texture is created, the RAM backing of MANAGED textures can be used in
21 * One way to reduce the virtual memory taken is to ignore lod and delete the RAM backing of
22 * MANAGED textures once it is uploaded. If the texture is read, or evicted from GPU memory, the RAM
23 …* backing would be recreated (Note that mapping the GPU memory is not acceptable as RAM memory is …
26 * Instead the approach taken here is to keep the RAM backing alive, but free its addressing space.
27 * In other words virtual memory usage is reduced, but the RAM usage of the app is the same.
29 * stored in RAM and visible only to the app. We can map/unmap portions of the file as we need.
[all …]
/third_party/backends/backend/genesys/
Dscanner_interface.h49 // GL646, GL841, GL843 have different ways to write to RAM and to gamma tables
56 // GL845, GL846, GL847 and GL124 have a uniform way to write to RAM tables

12345678910>>...36