| /linux-4.4.14/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-4.4.14/drivers/staging/media/mn88473/ |
| D | TODO | 14 checkpatch.pl tests. I don't want waste my time to review this kind of
|
| /linux-4.4.14/drivers/staging/media/mn88472/ |
| D | TODO | 14 checkpatch.pl tests. I don't want waste my time to review this kind of
|
| /linux-4.4.14/Documentation/usb/ |
| D | ehci.txt | 20 high speed "split transactions" that don't waste transfer bandwidth.
193 going to waste more than half the USB 2.0 bandwidth. Delays between the
196 sequence of 128 KB chunks would waste a lot less.
|
| /linux-4.4.14/Documentation/block/ |
| D | deadline-iosched.txt | 66 may even know that it is a waste of time to spend any time attempting to
|
| /linux-4.4.14/lib/raid6/ |
| D | int.uc | 46 * is just a waste of space.
|
| /linux-4.4.14/arch/sparc/kernel/ |
| D | wof.S | 122 WRITE_PAUSE ! waste some time
|
| /linux-4.4.14/Documentation/sound/alsa/soc/ |
| D | overview.txt | 21 recording) audio. This is fine for a PC, but tends to waste a lot of
|
| /linux-4.4.14/mm/ |
| D | zsmalloc.c | 756 int waste, usedpc; in get_pages_per_zspage() local
759 waste = zspage_size % class_size; in get_pages_per_zspage()
760 usedpc = (zspage_size - waste) * 100 / zspage_size; in get_pages_per_zspage()
|
| /linux-4.4.14/Documentation/ |
| D | xz.txt | 65 Double checking the integrity would probably be waste of CPU cycles.
|
| D | sysfs-rules.txt | 31 Parsing /proc/mounts is a waste of time. Other mount points are a
|
| D | IPMI.txt | 462 interface's performance. This can waste a lot of CPU and cause
466 value sets a balance between performance and CPU waste and needs to be
|
| D | ManagementStyle | 72 fairly easy to backtrack. Since you're not going to be able to waste
|
| D | xillybus.txt | 351 buffers, with a maximal waste of one page of memory.
|
| D | DMA-API-HOWTO.txt | 873 Therefore, keeping track of the mapping address and length is a waste
|
| D | CodingStyle | 448 write the code so that the _working_ is obvious, and it's a waste of
|
| D | SubmittingPatches | 462 counter-productive waste of time and energy. Rule (b) allows you to adjust
|
| /linux-4.4.14/Documentation/fb/ |
| D | modedb.txt | 7 which is a mess and a waste of resources. The main idea of modedb is to have
|
| /linux-4.4.14/drivers/mtd/chips/ |
| D | Kconfig | 170 in the programming of OTP bits will waste them.
|
| /linux-4.4.14/Documentation/vm/ |
| D | transhuge.txt | 170 max_ptes_none can waste cpu time very little, you can
178 A higher value can cause excessive swap IO and waste
|
| /linux-4.4.14/drivers/media/usb/pwc/ |
| D | philips.txt | 77 something more than 4 is an absolute waste. This memory is only
|
| /linux-4.4.14/Documentation/sh/ |
| D | new-machine.txt | 238 list. The method for doing this is self explanatory, and so we won't waste
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 3.Early-stage | 42 to communicate user requirements to these people is a waste of
|
| /linux-4.4.14/drivers/base/ |
| D | Kconfig | 315 for larger buffers it just a memory waste. With this parameter you can
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | cache.txt | 67 So large block sizes are bad because they waste cache space. And small
|
| /linux-4.4.14/drivers/usb/gadget/udc/ |
| D | Kconfig | 144 # don't waste memory for the other endpoints
|
| /linux-4.4.14/arch/arm/mm/ |
| D | Kconfig | 1061 another section-size padded region, so it can waste more memory
|
| /linux-4.4.14/Documentation/networking/ |
| D | packet_mmap.txt | 403 be a waste of memory.
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | README.OSS | 100 implemented there. In general it's a major waste of time to try to improve a
273 in SB mode but in general it's a complete waste of time. There are several
|
| /linux-4.4.14/Documentation/m68k/ |
| D | kernel-options.txt | 595 than 2 don't make sense, but waste memory. Otherwise, the maximum
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | cpusets.txt | 451 code might waste some compute cycles considering that possibility.
|
| /linux-4.4.14/arch/arm/ |
| D | Kconfig | 118 for larger buffers it just a waste of address space. Drivers which has
|
| /linux-4.4.14/Documentation/scsi/ |
| D | ncr53c8xx.txt | 1034 and delay data transfers or status/completions, and (b) may just waste
|
| /linux-4.4.14/Documentation/trace/ |
| D | ftrace.txt | 2843 waste it in functions. A kernel developer must be conscience of
|