Searched refs:charges (Results 1 – 5 of 5) sorted by relevance
| /Linux-v4.19/Documentation/cgroup-v1/ |
| 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
291 The main "kmem" counter is fed into the main counter, so kmem charges will
340 Since kmem charges will also be fed to the user counter and reclaim will be
431 You can move charges of a task along with task migration.
432 See 8. "Move charges at task migration"
465 Also, note that when memory.kmem.limit_in_bytes is set the charges due to
657 8. Move charges at task migration
659 Users can move charges associated with a task along with task migration, that
674 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-v4.19/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-v4.19/Documentation/admin-guide/ |
| D | cgroup-v2.rst | 2122 subject to a race condition, where concurrent charges could cause the
2124 limit to prevent new charges, and then reclaim and OOM kill until the
|
| /Linux-v4.19/drivers/isdn/hardware/eicon/ |
| D | message.c | 6071 static byte charges[5] = {4, 0, 0, 0, 0}; in SendInfo() local
6116 for (j = 0; j < 4; j++) charges[1 + j] = 0; in SendInfo()
6118 for (k = 1, j++; j < ie[0] && k <= 4; j++, k++) charges[k] = ie[1 + j]; in SendInfo()
6121 Info_Element = charges; in SendInfo()
|
