| /Linux-v5.4/tools/testing/selftests/rcutorture/bin/ |
| D | parse-console.sh | 115 summary=""
119 summary="$summary Badness: $n_badness"
124 summary="$summary Warnings: $n_warn"
129 summary="$summary Bugs: $n_bugs"
134 summary="$summary Call Traces: $n_calltrace"
139 summary="$summary lockdep: $n_badness"
144 summary="$summary Stalls: $n_stalls"
149 summary="$summary Starves: $n_starves"
151 print_warning Summary: $summary
|
| /Linux-v5.4/fs/jffs2/ |
| D | summary.c | 30 c->summary = kzalloc(sizeof(struct jffs2_summary), GFP_KERNEL); in jffs2_sum_init()
32 if (!c->summary) { in jffs2_sum_init()
37 c->summary->sum_buf = kmalloc(sum_size, GFP_KERNEL); in jffs2_sum_init()
39 if (!c->summary->sum_buf) { in jffs2_sum_init()
41 kfree(c->summary); in jffs2_sum_init()
54 jffs2_sum_disable_collecting(c->summary); in jffs2_sum_exit()
56 kfree(c->summary->sum_buf); in jffs2_sum_exit()
57 c->summary->sum_buf = NULL; in jffs2_sum_exit()
59 kfree(c->summary); in jffs2_sum_exit()
60 c->summary = NULL; in jffs2_sum_exit()
[all …]
|
| D | nodemgmt.c | 339 jffs2_sum_reset_collected(c->summary); /* reset collected summary */ in jffs2_find_nextblock()
368 reserved_size = PAD(sumsize + c->summary->sum_size + JFFS2_SUMMARY_FRAME_SIZE); in jffs2_do_reserve_space()
372 c->summary->sum_size, sumsize); in jffs2_do_reserve_space()
377 if (jeb && (PAD(minsize) + PAD(c->summary->sum_size + sumsize + in jffs2_do_reserve_space()
381 if (jffs2_sum_is_disabled(c->summary)) { in jffs2_do_reserve_space()
393 if (jffs2_sum_is_disabled(c->summary)) { in jffs2_do_reserve_space()
404 reserved_size = PAD(sumsize + c->summary->sum_size + JFFS2_SUMMARY_FRAME_SIZE); in jffs2_do_reserve_space()
|
| D | Makefile | 22 jffs2-$(CONFIG_JFFS2_SUMMARY) += summary.o
|
| D | Kconfig | 54 bool "JFFS2 summary support"
58 This feature makes it possible to use summary information
61 The summary information can be inserted into a filesystem image
|
| D | jffs2_fs_sb.h | 142 struct jffs2_summary *summary; /* Summary information */ member
|
| /Linux-v5.4/net/rxrpc/ |
| D | input.c | 40 struct rxrpc_ack_summary *summary, in rxrpc_congestion_management() argument
48 summary->flight_size = in rxrpc_congestion_management()
49 (call->tx_top - call->tx_hard_ack) - summary->nr_acks; in rxrpc_congestion_management()
52 summary->retrans_timeo = true; in rxrpc_congestion_management()
54 summary->flight_size / 2, 2); in rxrpc_congestion_management()
64 cumulative_acks += summary->nr_new_acks; in rxrpc_congestion_management()
65 cumulative_acks += summary->nr_rot_new_acks; in rxrpc_congestion_management()
69 summary->mode = call->cong_mode; in rxrpc_congestion_management()
70 summary->cwnd = call->cong_cwnd; in rxrpc_congestion_management()
71 summary->ssthresh = call->cong_ssthresh; in rxrpc_congestion_management()
[all …]
|
| /Linux-v5.4/Documentation/translations/ja_JP/ |
| D | SubmittingPatches | 471 Subject: [PATCH 001/123] subsystem: summary phrase
499 電子メールのサブジェクトの「summary phrase」はそのパッチの概要を正確
500 に表現しなければなりません。「summary phrase」をファイル名にしてはい
501 けません。パッチシリーズ中でそれぞれのパッチは同じ「summary phrase」を
505 あなたの電子メールの「summary phrase」がそのパッチにとって世界で唯一の識別子に
506 なるように心がけてください。「summary phrase」は git のチェンジログの中へ
507 ずっと伝播していきます。「summary phrase」は、開発者が後でパッチを参照する
509 人々はそのパッチに関連した議論を読むために「summary phrase」を使って google で
514 これらの理由のため、「summary phrase」はなぜパッチが必要であるか、パッチが何を
516 「summary phrase」は簡潔であり説明的である表現を目指しつつ、うまく
[all …]
|
| /Linux-v5.4/tools/perf/ |
| D | builtin-bench.c | 33 const char *summary; member
81 const char *summary; member
114 printf("%14s: %s\n", bench->name, bench->summary); in dump_benchmarks()
149 printf("%14s: %s\n", coll->name, coll->summary); in print_usage()
|
| D | builtin-data.c | 16 const char *summary; member
45 printf("\t %s\t- %s\n", cmd->name, cmd->summary); in print_usage()
|
| /Linux-v5.4/Documentation/hwmon/ |
| D | smm665.rst | 14 http://www.summitmicro.com/prod_select/summary/SMM465/SMM465DS.pdf
24 http://www.summitmicro.com/prod_select/summary/SMM665/SMM665B_2089_20.pdf
34 http://www.summitmicro.com/prod_select/summary/SMM665C/SMM665C_2125.pdf
44 http://www.summitmicro.com/prod_select/summary/SMM764/SMM764_2098.pdf
54 http://www.summitmicro.com/prod_select/summary/SMM766/SMM766_2086.pdf
56 http://www.summitmicro.com/prod_select/summary/SMM766B/SMM766B_2122.pdf
|
| /Linux-v5.4/tools/perf/Documentation/ |
| D | perf-sched.txt | 122 --summary::
123 Show only a summary of scheduling by thread with min, max, and average
127 --with-summary::
128 Show all scheduling events followed by a summary by thread with min,
|
| D | perf-trace.txt | 118 Accrue thread runtime and provide a summary at the end of the session.
135 --summary::
136 Show only a summary of syscalls by thread with min, max, and average times
140 --with-summary::
141 Show all syscalls followed by a summary by thread with min, max, and
|
| /Linux-v5.4/Documentation/driver-api/soundwire/ |
| D | index.rst | 8 summary
|
| /Linux-v5.4/Documentation/spi/ |
| D | index.rst | 10 spi-summary
|
| /Linux-v5.4/scripts/package/ |
| D | snapcraft.template | 3 summary: Linux kernel
|
| /Linux-v5.4/arch/powerpc/tools/ |
| D | checkpatch.sh | 11 --no-summary \
|
| /Linux-v5.4/Documentation/admin-guide/cifs/ |
| D | changes.rst | 5 See https://wiki.samba.org/index.php/LinuxCIFSKernel for summary
|
| /Linux-v5.4/Documentation/i2c/ |
| D | index.rst | 23 summary
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | index.rst | 21 api-summary
|
| /Linux-v5.4/arch/alpha/include/asm/ |
| D | core_titan.h | 336 u64 summary; /* 0x00 */ member
353 u64 summary; /* 0x00 */ member
|
| /Linux-v5.4/kernel/debug/kdb/ |
| D | kdb_cmds | 13 -summary
|
| /Linux-v5.4/Documentation/dev-tools/ |
| D | kselftest.rst | 61 Kselftest supports "summary" option to make it easier to understand the test
63 /tmp/testname file(s) when summary option is specified. This is applicable
66 To run kselftest with summary option enabled ::
68 $ make summary=1 kselftest
|
| /Linux-v5.4/Documentation/networking/ |
| D | nf_flowtable.txt | 105 made a very complete and comprehensive summary called "A state of network
107 mailined [3] and it also makes a rough summary of this work [4].
|
| /Linux-v5.4/Documentation/process/ |
| D | submitting-patches.rst | 168 SHA-1 ID of the commit. Please also include the oneline summary of
185 the SHA-1 ID, and the one line summary. Do not split the tag across multiple
658 Subject: [PATCH 001/123] subsystem: summary phrase
687 The ``summary phrase`` in the email's Subject should concisely
688 describe the patch which that email contains. The ``summary
689 phrase`` should not be a filename. Do not use the same ``summary
693 Bear in mind that the ``summary phrase`` of your email becomes a
695 into the ``git`` changelog. The ``summary phrase`` may later be used in
697 google for the ``summary phrase`` to read discussion regarding that
703 For these reasons, the ``summary`` must be no more than 70-75
[all …]
|
