| /Linux-v5.15/fs/jffs2/ |
| D | nodemgmt.c | 408 uint32_t waste; in jffs2_do_reserve_space() local
436 waste = jeb->free_size; in jffs2_do_reserve_space()
438 (jeb->offset + c->sector_size - waste) | REF_OBSOLETE, in jffs2_do_reserve_space()
439 waste, NULL); in jffs2_do_reserve_space()
441 jeb->dirty_size -= waste; in jffs2_do_reserve_space()
442 c->dirty_size -= waste; in jffs2_do_reserve_space()
443 jeb->wasted_size += waste; in jffs2_do_reserve_space()
444 c->wasted_size += waste; in jffs2_do_reserve_space()
|
| D | wbuf.c | 658 uint32_t waste = c->wbuf_pagesize - c->wbuf_len; in __jffs2_flush_wbuf() local
667 if (wbuf_jeb->free_size < waste) { in __jffs2_flush_wbuf()
669 c->wbuf_ofs, c->wbuf_len, waste); in __jffs2_flush_wbuf()
677 jffs2_link_node_ref(c, wbuf_jeb, (c->wbuf_ofs + c->wbuf_len) | REF_OBSOLETE, waste, NULL); in __jffs2_flush_wbuf()
679 wbuf_jeb->dirty_size -= waste; in __jffs2_flush_wbuf()
680 c->dirty_size -= waste; in __jffs2_flush_wbuf()
681 wbuf_jeb->wasted_size += waste; in __jffs2_flush_wbuf()
682 c->wasted_size += waste; in __jffs2_flush_wbuf()
|
| /Linux-v5.15/drivers/net/ethernet/qlogic/qed/ |
| D | qed_cxt.h | 26 u32 waste; member
|
| /Linux-v5.15/Documentation/maintainer/ |
| D | modifying-patches.rst | 10 to rediff, but this is a totally counter-productive waste of time and energy.
|
| /Linux-v5.15/Documentation/usb/ |
| D | ehci.rst | 24 high speed "split transactions" that don't waste transfer bandwidth.
207 going to waste more than half the USB 2.0 bandwidth. Delays between the
210 sequence of 128 KB chunks would waste a lot less.
|
| /Linux-v5.15/Documentation/block/ |
| D | deadline-iosched.rst | 65 may even know that it is a waste of time to spend any time attempting to
|
| /Linux-v5.15/lib/raid6/ |
| D | int.uc | 46 * is just a waste of space.
|
| /Linux-v5.15/Documentation/sound/soc/ |
| D | overview.rst | 22 recording) audio. This is fine for a PC, but tends to waste a lot of
|
| /Linux-v5.15/arch/sparc/kernel/ |
| D | wof.S | 123 WRITE_PAUSE ! waste some time
|
| /Linux-v5.15/kernel/dma/ |
| D | Kconfig | 199 for larger buffers it just a memory waste. With this parameter you can
|
| /Linux-v5.15/Documentation/staging/ |
| D | xz.rst | 68 Double checking the integrity would probably be waste of CPU cycles.
|
| /Linux-v5.15/mm/ |
| D | zsmalloc.c | 802 int waste, usedpc; in get_pages_per_zspage() local
805 waste = zspage_size % class_size; in get_pages_per_zspage()
806 usedpc = (zspage_size - waste) * 100 / zspage_size; in get_pages_per_zspage()
|
| /Linux-v5.15/Documentation/accounting/ |
| D | psi.rst | 54 actual CPU cycles are going to waste, and a workload that spends
|
| /Linux-v5.15/Documentation/fb/ |
| D | modedb.rst | 7 which is a mess and a waste of resources. The main idea of modedb is to have
|
| /Linux-v5.15/Documentation/x86/ |
| D | cpuinfo.rst | 56 has only one feature and would waste 31 bits of space in the x86_capability[]
|
| /Linux-v5.15/Documentation/core-api/ |
| D | kernel-api.rst | 341 clocks are disabled, so the system doesn't waste power changing the
|
| /Linux-v5.15/Documentation/admin-guide/mm/ |
| D | transhuge.rst | 210 max_ptes_none can waste cpu time very little, you can
218 A higher value can cause excessive swap IO and waste
|
| /Linux-v5.15/drivers/mtd/chips/ |
| D | Kconfig | 176 in the programming of OTP bits will waste them.
|
| /Linux-v5.15/Documentation/sh/ |
| D | new-machine.rst | 234 list. The method for doing this is self explanatory, and so we won't waste
|
| /Linux-v5.15/Documentation/admin-guide/media/ |
| D | philips.rst | 83 something more than 4 is an absolute waste. This memory is only
|
| /Linux-v5.15/Documentation/admin-guide/ |
| D | sysfs-rules.rst | 32 Parsing ``/proc/mounts`` is a waste of time. Other mount points are a
|
| /Linux-v5.15/Documentation/process/ |
| D | 3.Early-stage.rst | 46 to communicate user requirements to these people is a waste of
|
| /Linux-v5.15/Documentation/admin-guide/pm/ |
| D | cpuidle.rst | 224 would be a waste of time, even though the timer hardware may not need to be
232 waste of time and in this case the timer hardware would need to be reprogrammed,
235 in the shallow idle state selected by the governor, which will be a waste of
|
| /Linux-v5.15/Documentation/admin-guide/device-mapper/ |
| D | cache.rst | 74 So large block sizes are bad because they waste cache space. And small
|
| /Linux-v5.15/Documentation/driver-api/ |
| D | ipmi.rst | 469 interface's performance. This can waste a lot of CPU and cause
473 value sets a balance between performance and CPU waste and needs to be
|
