/linux-5.19.10/Documentation/translations/zh_CN/admin-guide/mm/damon/ |
D | usage.rst | 75 │ │ │ │ │ schemes/nr_schemes 131 ``targets``, 和 ``schemes``)。 189 contexts/<N>/schemes/ 199 schemes/<N>/ 215 schemes/<N>/access_pattern/ 225 schemes/<N>/quotas/ 244 schemes/<N>/watermarks/ 262 schemes/<N>/stats/ 285 # echo 1 > kdamonds/0/contexts/0/schemes/nr_schemes 286 # cd kdamonds/0/contexts/0/schemes/0 [all …]
|
D | start.rst | 132 $ damo schemes -c test_scheme <pid of your workload>
|
/linux-5.19.10/Documentation/ABI/testing/ |
D | sysfs-kernel-mm-damon | 29 file updates contents of schemes stats files of the kdamond. 135 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/nr_schemes 140 of the context named '0' to 'N-1' under the schemes/ directory. 142 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/action 148 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/access_pattern/sz/min 154 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/access_pattern/sz/max 160 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/access_pattern/nr_accesses/… 166 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/access_pattern/nr_accesses/… 172 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/access_pattern/age/min 178 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/access_pattern/age/max [all …]
|
/linux-5.19.10/mm/damon/ |
D | dbgfs.c | 154 static void free_schemes_arr(struct damos **schemes, ssize_t nr_schemes) in free_schemes_arr() argument 159 kfree(schemes[i]); in free_schemes_arr() 160 kfree(schemes); in free_schemes_arr() 187 struct damos *scheme, **schemes; in str_to_schemes() local 194 schemes = kmalloc_array(max_nr_schemes, sizeof(scheme), in str_to_schemes() 196 if (!schemes) in str_to_schemes() 231 schemes[*nr_schemes] = scheme; in str_to_schemes() 234 return schemes; in str_to_schemes() 236 free_schemes_arr(schemes, *nr_schemes); in str_to_schemes() 245 struct damos **schemes; in dbgfs_schemes_write() local [all …]
|
D | sysfs.c | 963 static void damon_sysfs_schemes_rm_dirs(struct damon_sysfs_schemes *schemes) in damon_sysfs_schemes_rm_dirs() argument 965 struct damon_sysfs_scheme **schemes_arr = schemes->schemes_arr; in damon_sysfs_schemes_rm_dirs() 968 for (i = 0; i < schemes->nr; i++) { in damon_sysfs_schemes_rm_dirs() 972 schemes->nr = 0; in damon_sysfs_schemes_rm_dirs() 974 schemes->schemes_arr = NULL; in damon_sysfs_schemes_rm_dirs() 977 static int damon_sysfs_schemes_add_dirs(struct damon_sysfs_schemes *schemes, in damon_sysfs_schemes_add_dirs() argument 983 damon_sysfs_schemes_rm_dirs(schemes); in damon_sysfs_schemes_add_dirs() 991 schemes->schemes_arr = schemes_arr; in damon_sysfs_schemes_add_dirs() 996 damon_sysfs_schemes_rm_dirs(schemes); in damon_sysfs_schemes_add_dirs() 1001 &damon_sysfs_scheme_ktype, &schemes->kobj, in damon_sysfs_schemes_add_dirs() [all …]
|
D | core.c | 281 list_add_tail(&s->list, &ctx->schemes); in damon_add_scheme() 376 INIT_LIST_HEAD(&ctx->schemes); in damon_new_ctx() 449 int damon_set_schemes(struct damon_ctx *ctx, struct damos **schemes, in damon_set_schemes() argument 458 damon_add_scheme(ctx, schemes[i]); in damon_set_schemes()
|
/linux-5.19.10/include/linux/ |
D | damon.h | 445 struct list_head schemes; member 476 list_for_each_entry(s, &(ctx)->schemes, list) 479 list_for_each_entry_safe(s, next, &(ctx)->schemes, list) 523 struct damos **schemes, ssize_t nr_schemes);
|
/linux-5.19.10/Documentation/admin-guide/mm/damon/ |
D | usage.rst | 81 │ │ │ │ │ schemes/nr_schemes 148 and three directories (``monitoring_attrs``, ``targets``, and ``schemes``) 238 contexts/<N>/schemes/ 244 schemes from the user and applies those to the target memory regions. Users 245 can get and set the schemes by reading from and writing to files under this 252 schemes/<N>/ 269 schemes/<N>/access_pattern/ 283 schemes/<N>/quotas/ 309 schemes/<N>/watermarks/ 334 schemes/<N>/stats/ [all …]
|
D | start.rst | 134 $ damo schemes -c test_scheme <pid of your workload>
|
/linux-5.19.10/drivers/net/ethernet/freescale/fman/ |
D | fman_keygen.c | 257 struct keygen_scheme schemes[FM_KG_MAX_NUM_OF_SCHEMES]; member 450 if (!keygen->schemes[i].used) { in get_free_scheme_id() 472 return &keygen->schemes[scheme_id]; in get_scheme()
|
/linux-5.19.10/Documentation/mips/ |
D | booting.rst | 8 Both schemes are supported; CONFIG_BOOT_RAW=y and CONFIG_NO_EXCEPT_FILL=y,
|
/linux-5.19.10/security/smack/ |
D | Kconfig | 13 of other mandatory security schemes.
|
/linux-5.19.10/Documentation/admin-guide/LSM/ |
D | Smack.rst | 348 Computer systems employ a variety of schemes to constrain how information is 349 shared among the people and services using the machine. Some of these schemes 351 access to pieces of data. These schemes are called discretionary access 353 of the user. Other schemes do not leave the decision regarding what a user or 354 program can access up to users or programs. These schemes are called mandatory 502 be "born" highly classified. To accommodate such schemes Smack includes a 552 schemes and concepts from other systems. Most often, the other systems are 650 of systems that use compatible labeling schemes, and the DOI specified on the
|
/linux-5.19.10/Documentation/devicetree/bindings/reset/ |
D | reset.txt | 17 are dictated by the binding of the reset provider, although common schemes
|
/linux-5.19.10/Documentation/driver-api/fpga/ |
D | fpga-region.rst | 19 is intended to be used by other schemes that have other ways of accomplishing
|
/linux-5.19.10/Documentation/infiniband/ |
D | tag_matching.rst | 25 Implementations frequently use different matching schemes for these two
|
/linux-5.19.10/fs/f2fs/ |
D | Kconfig | 25 the internal geometry or flash memory management schemes aka FTL, F2FS
|
/linux-5.19.10/Documentation/i2c/ |
D | fault-codes.rst | 13 faults. There may be fancier recovery schemes that are appropriate in
|
/linux-5.19.10/Documentation/driver-api/gpio/ |
D | intro.rst | 50 value might be driven, supporting "wire-OR" and similar schemes for the
|
/linux-5.19.10/Documentation/driver-api/cxl/ |
D | memory-devices.rst | 200 The port metadata and potential decode schemes that a give memory device may
|
/linux-5.19.10/Documentation/trace/coresight/ |
D | coresight-cpu-debug.rst | 93 schemes and finally this heavily impacts external debug module. So we can
|
/linux-5.19.10/Documentation/ABI/obsolete/ |
D | sysfs-driver-hid-roccat-isku | 149 Description: When written, this file lets one trigger temporary color schemes
|
/linux-5.19.10/Documentation/userspace-api/media/rc/ |
D | rc-protos.rst | 80 schemes. This bit is stored in bit 6 of the scancode, inverted. This is
|
/linux-5.19.10/Documentation/driver-api/ |
D | mtdnand.rst | 611 has built in default placement schemes for the various chiptypes. If due 618 Placement schemes are defined by a nand_oobinfo structure 690 Spare area autoplacement default schemes
|
/linux-5.19.10/block/partitions/ |
D | Kconfig | 16 the questions about foreign partitioning schemes.
|