Searched refs:charges (Results 1 – 5 of 5) sorted by relevance
| /linux-4.4.14/Documentation/cgroups/ |
| D | memory.txt | 77 memory.move_charge_at_immigrate # set/show controls of moving charges
206 be backed into memory in force, charges for pages are accounted against the
299 The main "kmem" counter is fed into the main counter, so kmem charges will
348 Since kmem charges will also be fed to the user counter and reclaim will be
439 You can move charges of a task along with task migration.
440 See 8. "Move charges at task migration"
473 Also, note that when memory.kmem.limit_in_bytes is set the charges due to
665 8. Move charges at task migration
667 Users can move charges associated with a task along with task migration, that
682 of charges should be moved. See 8.2 for details.
[all …]
|
| D | memcg_test.txt | 61 (a) If the SwapCache is newly allocated and read, it has no charges.
244 9.9 Move charges at task migration
257 You can see charges have been moved by reading *.usage_in_bytes or
|
| /linux-4.4.14/Documentation/power/ |
| D | power_supply_class.txt | 50 All voltages, currents, charges, energies, time and temperatures in µV,
80 This defines trickle and fast charges. For batteries that
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | logfs.txt | 142 this and charges for the uncompressed size. Failing to do so could
|
| /linux-4.4.14/drivers/isdn/hardware/eicon/ |
| D | message.c | 6201 static byte charges[5] = {4, 0, 0, 0, 0}; in SendInfo() local
6246 for (j = 0; j < 4; j++) charges[1 + j] = 0; in SendInfo()
6248 for (k = 1, j++; j < ie[0] && k <= 4; j++, k++) charges[k] = ie[1 + j]; in SendInfo()
6251 Info_Element = charges; in SendInfo()
|