/openbmc/linux/kernel/trace/ |
H A D | ring_buffer_benchmark.c | 235 unsigned long long overruns; in ring_buffer_producer() local 300 overruns = ring_buffer_overruns(buffer); in ring_buffer_producer() 326 trace_printk("Overruns: %lld\n", overruns); in ring_buffer_producer() 333 trace_printk("Total: %lld\n", entries + overruns + read); in ring_buffer_producer()
|
H A D | ring_buffer.c | 4372 unsigned long overruns = 0; in ring_buffer_overruns() local 4378 overruns += local_read(&cpu_buffer->overrun); in ring_buffer_overruns() 4381 return overruns; in ring_buffer_overruns()
|
/openbmc/linux/Documentation/networking/device_drivers/appletalk/ |
H A D | cops.rst | 55 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 56 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 coll:0
|
/openbmc/linux/drivers/vdpa/vdpa_sim/ |
H A D | vdpa_sim_net.c | 46 u64 overruns; member 281 net->rx_stats.overruns += rx_overruns; in vdpasim_net_work() 303 rx_overruns = net->rx_stats.overruns; in vdpasim_net_get_stats()
|
/openbmc/linux/Documentation/spi/ |
H A D | pxa2xx.rst | 109 FIFO overruns (especially in PIO mode transfers). Good default values are::
|
/openbmc/linux/arch/x86/boot/ |
H A D | header.S | 441 # pointer overruns the input pointer.
|
/openbmc/linux/arch/arm/boot/dts/arm/ |
H A D | arm-realview-eb.dtsi | 337 /* Due to frequent FIFO overruns, use just 500 kHz */
|
H A D | arm-realview-pbx.dtsi | 535 /* Due to frequent FIFO overruns, use just 500 kHz */
|
H A D | arm-realview-pb1176.dts | 513 /* Due to frequent FIFO overruns, use just 500 kHz */
|
H A D | arm-realview-pb11mp.dts | 486 /* Due to frequent FIFO overruns, use just 500 kHz */
|
/openbmc/linux/Documentation/networking/device_drivers/hamradio/ |
H A D | z8530drv.rst | 413 RxOver number of receiver overruns 644 port. If it shows under- and overruns you own such a system.
|
/openbmc/linux/Documentation/networking/device_drivers/can/ |
H A D | can327.rst | 264 overruns. It may abort sending in the middle of the line, which will
|
/openbmc/libpldm/ |
H A D | CHANGELOG.md | 352 eliminates the opportunity for buffer overruns when extracting objects from
|
/openbmc/linux/Documentation/networking/ |
H A D | bonding.rst | 1866 RX packets:7224794 errors:0 dropped:0 overruns:0 frame:0 1867 TX packets:3286647 errors:1 dropped:0 overruns:1 carrier:0 1872 RX packets:3573025 errors:0 dropped:0 overruns:0 frame:0 1873 TX packets:1643167 errors:1 dropped:0 overruns:1 carrier:0 1879 RX packets:3651769 errors:0 dropped:0 overruns:0 frame:0 1880 TX packets:1643480 errors:0 dropped:0 overruns:0 carrier:0
|
/openbmc/qemu/docs/devel/migration/ |
H A D | main.rst | 121 into buffers and the like can't cause overruns. Fail the incoming migration
|
/openbmc/linux/drivers/scsi/aic7xxx/ |
H A D | aic79xx.seq | 2119 * None-the-less, we must still catch and report overruns to 2142 * Status PKT overruns are uncerimoniously recovered with a
|
H A D | aic7xxx.seq | 885 /* Guard against overruns */
|
H A D | aic79xx.reg | 4230 * avoid the persistent sync offset overruns.
|
/openbmc/linux/Documentation/kernel-hacking/ |
H A D | hacking.rst | 257 overruns. Make sure that will be enough.
|
/openbmc/linux/Documentation/arch/m68k/ |
H A D | kernel-options.rst | 563 overruns. Lower values give a slightly faster mouse responses and
|
/openbmc/linux/Documentation/scheduler/ |
H A D | sched-deadline.rst | 121 to get informed about runtime overruns through the delivery of SIGXCPU
|
/openbmc/linux/Documentation/scsi/ |
H A D | scsi_mid_low_api.rst | 1197 underruns (overruns should not be reported). An LLD
|
/openbmc/linux/Documentation/arch/sparc/oradax/ |
H A D | dax-hv-api.txt | 384 to protect against buffer overruns.
|
/openbmc/openbmc/poky/documentation/profile-manual/ |
H A D | usage.rst | 1023 application is causing buffer I/O overruns, it probably means that
|
/openbmc/linux/Documentation/filesystems/ |
H A D | xfs-online-fsck-design.rst | 2841 the transactions to avoid overruns.
|