| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-kernel-mm-damon | 29 file updates contents of schemes stats files of the kdamond.
141 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/nr_schemes
146 of the context named '0' to 'N-1' under the schemes/ directory.
148 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/action
154 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/access_pattern/sz/min
160 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/access_pattern/sz/max
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/nr_accesses/…
178 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/access_pattern/age/min
184 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/access_pattern/age/max
[all …]
|
| /kernel/linux/linux-6.6/Documentation/translations/zh_CN/admin-guide/mm/damon/ |
| D | usage.rst | 75 │ │ │ │ │ schemes/nr_schemes
138 ``targets``, 和 ``schemes``)。
198 contexts/<N>/schemes/
208 schemes/<N>/
226 schemes/<N>/access_pattern/
236 schemes/<N>/quotas/
255 schemes/<N>/watermarks/
273 schemes/<N>/stats/
284 schemes/<N>/tried_regions/
314 # echo 1 > kdamonds/0/contexts/0/schemes/nr_schemes
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mtd/ |
| D | gpmc-nand.txt | 113 support ecc-schemes with hardware error-correction (BCHx_HW). However
114 such SoC can use ecc-schemes with software library for error-correction
121 Higher ECC schemes require more OOB/Spare area to store ECC syndrome,
131 '3' for HAM1_xx ecc schemes
132 '7' for BCH4_xx ecc schemes
133 '14' for BCH8_xx ecc schemes
134 '26' for BCH16_xx ecc schemes
141 probably use lower ecc-schemes like BCH8.
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/mm/damon/ |
| D | usage.rst | 78 │ │ │ │ │ schemes/nr_schemes
163 and three directories (``monitoring_attrs``, ``targets``, and ``schemes``)
258 contexts/<N>/schemes/
261 The directory for DAMON-based Operation Schemes (:ref:`DAMOS
262 <damon_design_damos>`). Users can get and set the schemes by reading from and
269 schemes/<N>/
300 schemes/<N>/access_pattern/
313 schemes/<N>/quotas/
336 schemes/<N>/watermarks/
355 schemes/<N>/filters/
[all …]
|
| /kernel/linux/linux-6.6/drivers/net/ethernet/freescale/fman/ |
| D | fman_keygen.c | 15 /* Maximum number of KeyGen Schemes */
201 * schemes sharing between multiple ports is not
230 struct keygen_scheme schemes[FM_KG_MAX_NUM_OF_SCHEMES]; member
231 /* Array of schemes */
283 * Build Action Register value for port binding to schemes
361 * Write all Schemes Registers with specified values
416 * Return: 0 on success, -EINVAL when the are no available free schemes
423 if (!keygen->schemes[i].used) { in get_free_scheme_id()
445 return &keygen->schemes[scheme_id]; in get_scheme()
450 * Bind the port to schemes
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/freescale/fman/ |
| D | fman_keygen.c | 42 /* Maximum number of KeyGen Schemes */
228 * schemes sharing between multiple ports is not
257 struct keygen_scheme schemes[FM_KG_MAX_NUM_OF_SCHEMES]; member
258 /* Array of schemes */
310 * Build Action Register value for port binding to schemes
388 * Write all Schemes Registers with specified values
443 * Return: 0 on success, -EINVAL when the are no available free schemes
450 if (!keygen->schemes[i].used) { in get_free_scheme_id()
472 return &keygen->schemes[scheme_id]; in get_scheme()
477 * Bind the port to schemes
[all …]
|
| /kernel/linux/linux-6.6/tools/testing/selftests/damon/ |
| D | sysfs_update_removed_scheme_dir.sh | 29 echo 1 > "$damon_sysfs/kdamonds/0/contexts/0/schemes/nr_schemes"
30 scheme_dir="$damon_sysfs/kdamonds/0/contexts/0/schemes/0"
38 echo 0 > "$damon_sysfs/kdamonds/0/contexts/0/schemes/nr_schemes"
|
| D | debugfs_schemes.sh | 6 # Test schemes file
9 file="$DBGFS/schemes"
|
| /kernel/linux/linux-6.6/mm/damon/ |
| D | dbgfs.c | 193 static void free_schemes_arr(struct damos **schemes, ssize_t nr_schemes) in free_schemes_arr() argument
198 kfree(schemes[i]); in free_schemes_arr()
199 kfree(schemes); in free_schemes_arr()
235 struct damos *scheme, **schemes; in str_to_schemes() local
241 schemes = kmalloc_array(max_nr_schemes, sizeof(scheme), in str_to_schemes()
243 if (!schemes) in str_to_schemes()
285 schemes[*nr_schemes] = scheme; in str_to_schemes()
288 return schemes; in str_to_schemes()
290 free_schemes_arr(schemes, *nr_schemes); in str_to_schemes()
299 struct damos **schemes; in dbgfs_schemes_write() local
[all …]
|
| D | sysfs-schemes.c | 181 * schemes/stats directory
1380 * schemes directory
1388 void damon_sysfs_schemes_rm_dirs(struct damon_sysfs_schemes *schemes) in damon_sysfs_schemes_rm_dirs() argument
1390 struct damon_sysfs_scheme **schemes_arr = schemes->schemes_arr; in damon_sysfs_schemes_rm_dirs()
1393 for (i = 0; i < schemes->nr; i++) { in damon_sysfs_schemes_rm_dirs()
1397 schemes->nr = 0; in damon_sysfs_schemes_rm_dirs()
1399 schemes->schemes_arr = NULL; in damon_sysfs_schemes_rm_dirs()
1402 static int damon_sysfs_schemes_add_dirs(struct damon_sysfs_schemes *schemes, in damon_sysfs_schemes_add_dirs() argument
1408 damon_sysfs_schemes_rm_dirs(schemes); in damon_sysfs_schemes_add_dirs()
1416 schemes->schemes_arr = schemes_arr; in damon_sysfs_schemes_add_dirs()
[all …]
|
| D | sysfs.c | 637 struct damon_sysfs_schemes *schemes; member
694 struct damon_sysfs_schemes *schemes = damon_sysfs_schemes_alloc(); in damon_sysfs_context_set_schemes() local
697 if (!schemes) in damon_sysfs_context_set_schemes()
699 err = kobject_init_and_add(&schemes->kobj, &damon_sysfs_schemes_ktype, in damon_sysfs_context_set_schemes()
700 &context->kobj, "schemes"); in damon_sysfs_context_set_schemes()
702 kobject_put(&schemes->kobj); in damon_sysfs_context_set_schemes()
705 context->schemes = schemes; in damon_sysfs_context_set_schemes()
741 damon_sysfs_schemes_rm_dirs(context->schemes); in damon_sysfs_context_rm_dirs()
742 kobject_put(&context->schemes->kobj); in damon_sysfs_context_rm_dirs()
1008 * @DAMON_SYSFS_CMD_UPDATE_SCHEMES_TRIED_REGIONS: Update schemes tried
[all …]
|
| D | sysfs-common.h | 27 * schemes directory
37 void damon_sysfs_schemes_rm_dirs(struct damon_sysfs_schemes *schemes);
|
| D | Makefile | 6 obj-$(CONFIG_DAMON_SYSFS) += sysfs-common.o sysfs-schemes.o sysfs.o
|
| D | core.c | 339 list_add_tail(&s->list, &ctx->schemes); in damon_add_scheme()
443 INIT_LIST_HEAD(&ctx->schemes); in damon_new_ctx()
570 * damon_set_schemes() - Set data access monitoring based operation schemes.
572 * @schemes: array of the schemes
573 * @nr_schemes: number of entries in @schemes
578 void damon_set_schemes(struct damon_ctx *ctx, struct damos **schemes, in damon_set_schemes() argument
587 damon_add_scheme(ctx, schemes[i]); in damon_set_schemes()
1403 if (!list_empty(&ctx->schemes)) in kdamond_fn()
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | damon.h | 19 /* Max priority score for DAMON-based operation schemes */
311 * To do the work only when needed, schemes can be activated for specific
312 * system situations using &wmarks. If all schemes that registered to the
316 * If all schemes that registered to a &struct damon_ctx are inactive, DAMON
424 * @after_wmarks_check: Called after each schemes' watermarks check.
437 * operation schemes' watermarks check. If users need to make changes to the
519 * @schemes: Head of schemes (&damos) list.
548 struct list_head schemes; member
593 list_for_each_entry(s, &(ctx)->schemes, list)
596 list_for_each_entry_safe(s, next, &(ctx)->schemes, list)
[all …]
|
| /kernel/linux/linux-6.6/Documentation/mm/damon/ |
| D | design.rst | 223 Operation Schemes
236 One straightforward approach for such schemes would be profile-guided
246 effective, and therefore widely be used. However, implementing such schemes
254 Schemes (DAMOS). It lets users specify their desired schemes at a high
289 The access pattern of the schemes' interest. The patterns are constructed with
360 is activated. If all schemes are deactivated by the watermarks, the monitoring
377 To let users optimize DAMOS schemes with such special knowledge, DAMOS provides
389 list. Hence, users can apply specific schemes to only anonymous pages,
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/amdzen2/ |
| D | floating-point.json | 71 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
77 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
83 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
89 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/amdzen2/ |
| D | floating-point.json | 71 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
77 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
83 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
89 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
|
| /kernel/linux/linux-6.6/drivers/usb/musb/ |
| D | Makefile | 29 # possible I/O schemes will be enabled at a time ...
30 # PIO only, or DMA (several potential schemes).
|
| /kernel/linux/linux-5.10/drivers/usb/musb/ |
| D | Makefile | 30 # possible I/O schemes will be enabled at a time ...
31 # PIO only, or DMA (several potential schemes).
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/amdzen3/ |
| D | floating-point.json | 70 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
76 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
82 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
88 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/amdzen1/ |
| D | floating-point.json | 172 …g the effectiveness of the Move elimination and Scalar code optimization schemes. Number of Scalar…
179 …g the effectiveness of the Move elimination and Scalar code optimization schemes. Number of Ops th…
186 …g the effectiveness of the Move elimination and Scalar code optimization schemes. Number of SSE Mo…
193 …g the effectiveness of the Move elimination and Scalar code optimization schemes. Number of SSE Mo…
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/amdzen1/ |
| D | floating-point.json | 172 …g the effectiveness of the Move elimination and Scalar code optimization schemes. Number of Scalar…
179 …g the effectiveness of the Move elimination and Scalar code optimization schemes. Number of Ops th…
186 …g the effectiveness of the Move elimination and Scalar code optimization schemes. Number of SSE Mo…
193 …g the effectiveness of the Move elimination and Scalar code optimization schemes. Number of SSE Mo…
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-6.6/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
|