Home
last modified time | relevance | path

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

/linux/tools/perf/util/
H A 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);
H A Dsvghelper.c154 void svg_ubox(int Yslot, u64 start, u64 end, double height, const char *type, int fd, int err, int merges) in svg_ubox()
163 fprintf(svgfile, "<title>fd=%d error=%d merges=%d</title>\n", fd, err, merges); in svg_ubox()
173 void svg_lbox(int Yslot, u64 start, u64 end, double height, const char *type, int fd, int err, int merges) in svg_lbox()
182 fprintf(svgfile, "<title>fd=%d error=%d merges=%d</title>\n", fd, err, merges); in svg_lbox()
192 void svg_fbox(int Yslot, u64 start, u64 end, double height, const char *type, int fd, int err, int merges) in svg_fbox()
201 fprintf(svgfile, "<title>fd=%d error=%d merges=%d</title>\n", fd, err, merges); in svg_fbox()
153 svg_ubox(int Yslot,u64 start,u64 end,double height,const char * type,int fd,int err,int merges) svg_ubox() argument
172 svg_lbox(int Yslot,u64 start,u64 end,double height,const char * type,int fd,int err,int merges) svg_lbox() argument
191 svg_fbox(int Yslot,u64 start,u64 end,double height,const char * type,int fd,int err,int merges) svg_fbox() argument
/linux/Documentation/maintainer/
H A 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/Documentation/block/
H A 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
H A 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
H A Dbfq-iosched.rst227 - As CFQ, BFQ merges queues performing interleaved I/O, i.e.,
/linux/drivers/md/
H A Ddm-stats.c28 unsigned long long merges[2]; member
604 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/Documentation/admin-guide/
H A 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/Documentation/ABI/testing/
H A Dsysfs-firmware-memmap12 the kernel merges that memory map with other information or
/linux/Documentation/process/
H A 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/block/
H A Dblk-merge.c790 part_stat_inc(req->part, merges[op_stat_group(req_op(req))]); in blk_account_io_merge_request()
979 part_stat_inc(req->part, merges[op_stat_group(req_op(req))]); in blk_account_io_merge_bio()
/linux/Documentation/admin-guide/mm/
H A Dksm.rst25 KSM only merges anonymous (private) pages, never pagecache (file) pages.
96 When set to 0, ksm merges only pages which physically reside
/linux/Documentation/mm/
H A Dzsmalloc.rst103 As an optimization, zsmalloc merges size classes that have similar
/linux/Documentation/admin-guide/device-mapper/
H A Dsnapshot.rst83 procedure, and merges these chunks back into the <origin>. Once merging
/linux/Documentation/filesystems/xfs/
H A Dxfs-maintainer-entry-profile.rst78 - **Release Manager**: This person merges reviewed patchsets into an
/linux/Documentation/mm/damon/
H A Ddesign.rst215 adaptively merges and splits each region based on their access frequency.
220 by the ``minimum number of regions``, DAMON merges the two regions. If the
/linux/net/sched/
H A DKconfig393 queuing discipline that merges functionality of PRIO and DRR