| /linux/tools/perf/util/ |
| H A D | svghelper.h | 10 …_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);
|
| /linux/Documentation/maintainer/ |
| H A D | rebasing-and-merging.rst | 18 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/Documentation/block/ |
| H A D | stat.rst | 30 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
|
| H A D | deadline-iosched.rst | 64 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
|
| H A D | bfq-iosched.rst | 227 - As CFQ, BFQ merges queues performing interleaved I/O, i.e.,
|
| /linux/drivers/md/ |
| H A D | dm-stats.c | 28 unsigned long long merges[2]; member
606 p->merges[idx] += stats_aux->merged; in dm_stat_for_entry()
735 shared->tmp.merges[READ] = 0; in __dm_stat_init_temporary_percpu_totals()
736 shared->tmp.merges[WRITE] = 0; in __dm_stat_init_temporary_percpu_totals()
753 shared->tmp.merges[READ] += READ_ONCE(p->merges[READ]); in __dm_stat_init_temporary_percpu_totals()
754 shared->tmp.merges[WRITE] += READ_ONCE(p->merges[WRITE]); in __dm_stat_init_temporary_percpu_totals()
787 p->merges[READ] -= shared->tmp.merges[READ]; in __dm_stat_clear()
788 p->merges[WRITE] -= shared->tmp.merges[WRITE]; in __dm_stat_clear()
900 shared->tmp.merges[READ], in dm_stats_print()
904 shared->tmp.merges[WRITE], in dm_stats_print()
|
| /linux/block/ |
| H A D | genhd.c | 121 stat->merges[group] += ptr->merges[group]; in part_stat_read_all()
1081 stat.merges[STAT_READ], in part_stat_show()
1085 stat.merges[STAT_WRITE], in part_stat_show()
1096 stat.merges[STAT_DISCARD], in part_stat_show()
1386 seq_put_decimal_ull(seqf, " ", stat.merges[STAT_READ]); in diskstats_show()
1391 seq_put_decimal_ull(seqf, " ", stat.merges[STAT_WRITE]); in diskstats_show()
1403 seq_put_decimal_ull(seqf, " ", stat.merges[STAT_DISCARD]); in diskstats_show()
|
| H A D | blk-merge.c | 723 part_stat_inc(req->part, merges[op_stat_group(req_op(req))]); in blk_account_io_merge_request()
936 part_stat_inc(req->part, merges[op_stat_group(req_op(req))]); in blk_account_io_merge_bio()
|
| /linux/tools/perf/ |
| H A D | builtin-timechart.c | 171 int merges;
886 sample->merges += prev->merges + 1; in process_exit_write()
1218 sample->merges); in draw_io_bars()
1227 sample->merges); in draw_io_bars()
1236 sample->merges); in draw_io_bars()
1245 sample->merges); in draw_io_bars()
1254 sample->merges); in draw_process_bars()
1263 sample->merges); in draw_process_bars()
170 int merges; global() member
|
| /linux/include/linux/ |
| H A D | part_stat.h | 12 unsigned long merges[NR_STAT_GROUPS]; member
|
| /linux/Documentation/translations/pt_BR/process/ |
| H A D | 7.AdvancedTopics.rst | 45 branches, o index, fast-forward merges, pushes e pulls, detached HEADs, etc.
107 ser feito. Fazer merges ocasionalmente faz todo o sentido, mas merges excessivamente
109 caso é fazer merges raramente, e geralmente apenas em release points específicos
111 mudanças específicas, sempre poderá realizar merges de teste em uma branch
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-firmware-memmap | 12 the kernel merges that memory map with other information or
|
| /linux/Documentation/translations/zh_CN/ |
| H A D | how-to.rst | 260 # 请执行 git log --no-merges --oneline <您翻译的英文文档路径>
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | ksm.rst | 25 KSM only merges anonymous (private) pages, never pagecache (file) pages.
96 When set to 0, ksm merges only pages which physically reside
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | snapshot.rst | 83 procedure, and merges these chunks back into the <origin>. Once merging
|
| /linux/net/sched/ |
| H A D | Kconfig | 393 queuing discipline that merges functionality of PRIO and DRR
|