Home
last modified time | relevance | path

Searched refs:merges (Results 1 – 22 of 22) sorted by relevance

/Linux-v5.10/tools/perf/util/
Dsvghelper.h10 …_ubox(int Yslot, u64 start, u64 end, double height, const char *type, int fd, int err, int merges);
11 …_lbox(int Yslot, u64 start, u64 end, double height, const char *type, int fd, int err, int merges);
12 …_fbox(int Yslot, u64 start, u64 end, double height, const char *type, int fd, int err, int merges);
Dsvghelper.c153 …g_ubox(int Yslot, u64 start, u64 end, double height, const char *type, int fd, int err, int merges) in svg_ubox() argument
162 fprintf(svgfile, "<title>fd=%d error=%d merges=%d</title>\n", fd, err, merges); in svg_ubox()
172 …g_lbox(int Yslot, u64 start, u64 end, double height, const char *type, int fd, int err, int merges) in svg_lbox() argument
181 fprintf(svgfile, "<title>fd=%d error=%d merges=%d</title>\n", fd, err, merges); in svg_lbox()
191 …g_fbox(int Yslot, u64 start, u64 end, double height, const char *type, int fd, int err, int merges) in svg_fbox() argument
200 fprintf(svgfile, "<title>fd=%d error=%d merges=%d</title>\n", fd, err, merges); in svg_fbox()
/Linux-v5.10/Documentation/maintainer/
Drebasing-and-merging.rst18 merges would be nearly impossible. Some problems encountered by
19 maintainers result from a desire to avoid merges, while others come from
106 is not such a project; any rebasing of branches to avoid merges will, most
109 Subsystem maintainers find themselves having to do two types of merges:
138 While merges from downstream are common and unremarkable, merges from other
140 Such merges need to be carefully thought about and well justified, or
144 type of merge is often called a "back merge". Back merges can help to make
149 Why is that? Back merges will muddy the development history of your own
152 you are managing is stable and ready for upstream. Frequent merges can
157 That said, back merges are occasionally required; when that happens, be
[all …]
/Linux-v5.10/Documentation/block/
Dstat.rst30 read merges requests number of read I/Os merged with in-queue I/O
34 write merges requests number of write I/Os merged with in-queue I/O
41 discard merges requests number of discard I/Os merged with in-queue I/O
61 read merges, write merges, discard merges
Ddeadline-iosched.rst64 back merges are much more common than front merges. For some work loads, you
67 Front merges may still occur due to the cached last_merge hint, but since
Dqueue-sysfs.rst164 merging requests in the block layer. By default (0) all merges are
165 enabled. When set to 1 only simple one-hit merges will be tried. When
Dbiodoc.rst423 7. Ability to handle the possibility of splits/merges as the structure passes
482 - A linked list of bios is used as before for unrelated merges [#]_ - this
495 unrelated merges -- a request ends up containing two or more bios that
957 "Front merges", a new request being merged at the front of an existing request,
958 are far less common than "back merges" due to the nature of most I/O patterns.
959 Front merges are handled by the binary trees in AS and deadline schedulers.
Dinline-encryption.rst132 during bio and request merges).
Dbfq-iosched.rst227 - As CFQ, BFQ merges queues performing interleaved I/O, i.e.,
/Linux-v5.10/drivers/md/
Ddm-stats.c28 unsigned long long merges[2]; member
554 p->merges[idx] += stats_aux->merged; in dm_stat_for_entry()
684 shared->tmp.merges[READ] = 0; in __dm_stat_init_temporary_percpu_totals()
685 shared->tmp.merges[WRITE] = 0; in __dm_stat_init_temporary_percpu_totals()
702 shared->tmp.merges[READ] += READ_ONCE(p->merges[READ]); in __dm_stat_init_temporary_percpu_totals()
703 shared->tmp.merges[WRITE] += READ_ONCE(p->merges[WRITE]); in __dm_stat_init_temporary_percpu_totals()
735 p->merges[READ] -= shared->tmp.merges[READ]; in __dm_stat_clear()
736 p->merges[WRITE] -= shared->tmp.merges[WRITE]; in __dm_stat_clear()
846 shared->tmp.merges[READ], in dm_stats_print()
850 shared->tmp.merges[WRITE], in dm_stats_print()
/Linux-v5.10/include/linux/
Dpart_stat.h11 unsigned long merges[NR_STAT_GROUPS]; member
/Linux-v5.10/tools/perf/
Dbuiltin-timechart.c167 int merges; member
826 sample->merges += prev->merges + 1; in pid_end_io_sample()
1171 sample->merges); in draw_io_bars()
1180 sample->merges); in draw_io_bars()
1189 sample->merges); in draw_io_bars()
1198 sample->merges); in draw_io_bars()
1207 sample->merges); in draw_io_bars()
1216 sample->merges); in draw_io_bars()
/Linux-v5.10/block/
Dgenhd.c108 stat->merges[group] += ptr->merges[group]; in part_stat_read_all()
1309 stat.merges[STAT_READ], in part_stat_show()
1313 stat.merges[STAT_WRITE], in part_stat_show()
1324 stat.merges[STAT_DISCARD], in part_stat_show()
1633 stat.merges[STAT_READ], in diskstats_show()
1638 stat.merges[STAT_WRITE], in diskstats_show()
1650 stat.merges[STAT_DISCARD], in diskstats_show()
Dblk-merge.c684 part_stat_inc(req->part, merges[op_stat_group(req_op(req))]); in blk_account_io_merge_request()
909 part_stat_inc(req->part, merges[op_stat_group(req_op(req))]); in blk_account_io_merge_bio()
/Linux-v5.10/Documentation/ABI/testing/
Dsysfs-firmware-memmap12 the kernel merges that memory map with other information or
Dsysfs-block166 merge checks are disabled, but the simple one-shot merges
/Linux-v5.10/Documentation/admin-guide/
Diostats.rst155 the host disk happens much earlier. All merges and timings now happen
183 reads/writes before merges for partitions and after for disks. Since a
192 eventual merges. As requests can be merged across partition, this could lead
/Linux-v5.10/Documentation/process/
D7.AdvancedTopics.rst45 remote branches, the index, fast-forward merges, pushes and pulls, detached
106 makes good sense, but overly frequent merges can clutter the history
110 perform test merges in a private branch. The git "rerere" tool can be
/Linux-v5.10/Documentation/admin-guide/mm/
Dksm.rst27 KSM only merges anonymous (private) pages, never pagecache (file) pages.
95 When set to 0, ksm merges only pages which physically reside
/Linux-v5.10/Documentation/devicetree/bindings/sound/
Drenesas,rsnd.txt140 MIX merges 2 sounds path. You can see 2 sound interface on system,
191 TDM Split mode merges 4 sounds. You can see 4 sound interface on system,
/Linux-v5.10/Documentation/admin-guide/device-mapper/
Dsnapshot.rst83 procedure, and merges these chunks back into the <origin>. Once merging
/Linux-v5.10/net/sched/
DKconfig429 queuing discipline that merges functionality of PRIO and DRR