| /linux-4.4.14/drivers/net/ethernet/ti/ |
| D | netcp_xgbepcsr.c | 321 int loss, i, status = 1; in netcp_xgbe_check_link_status() local
325 loss = readl(serdes_regs + 0x1fc0 + 0x20 + (i * 0x04)) & 0x1; in netcp_xgbe_check_link_status()
342 if (!loss && blk_lock) { in netcp_xgbe_check_link_status()
|
| D | tlan.c | 2103 u32 excess_col, late_col, loss; in tlan_read_and_clear_stats() local
2132 loss = inb(dev->base_addr + TLAN_DIO_DATA + 2); in tlan_read_and_clear_stats()
2138 dev->stats.tx_errors += tx_under + loss; in tlan_read_and_clear_stats()
2147 dev->stats.tx_carrier_errors += loss; in tlan_read_and_clear_stats()
|
| /linux-4.4.14/Documentation/networking/ |
| D | x25-iface.txt | 96 The probability of packet loss due to backlog congestion can be
103 This will reliably suppress packet loss. The LAPB protocol will
117 This will not reliably avoid packet loss, but the probability
118 of packet loss in netif_rx() path will be significantly reduced.
|
| D | tcp-thin.txt | 9 on the data delivery latency, packet loss can be devastating for
|
| D | igb.txt | 58 poor performance or loss of link.
|
| D | xfrm_sync.txt | 15 with as minimal loss at failover time.
|
| D | 6pack.txt | 145 bad checksum', which is due to data loss if the other station sends two
|
| D | README.ipw2100 | 220 the PSP protocol you may experience packet loss or very poor performance
|
| D | e1000e.txt | 263 poor performance or loss of link.
|
| D | cxgb.txt | 103 and is done at "YOUR OWN RISK". Chelsio will not be held responsible for loss
|
| D | rds.txt | 202 into memory. This creates a potential message loss if the HCA is
|
| D | ip-sysctl.txt | 101 unexpected packet loss. The current default value is calculated
243 Tail loss probe (TLP) that converts RTOs occurring due to tail
244 losses into fast recovery (draft-dukkipati-tcpm-tcp-loss-probe-01).
437 This value is a bitmap to enable various experimental loss recovery
440 RACK: 0x1 enables the RACK loss detection for fast detection of lost
|
| D | e1000.txt | 424 poor performance or loss of link.
|
| D | bonding.txt | 466 susceptible to loss of the gratuitous ARP, and an
1926 detect carrier loss on the device (e.g., when the cable is physically
2658 monitor will reliably detect link loss to an external switch. This is
2673 ethernet (eth0) only, therefore, any loss of link to eth0 will result
2729 resulting degradation of performance. The precise performance loss
|
| D | packet_mmap.txt | 999 packet are not buffered, tc disciplines are ignored, increased loss can occur
|
| D | arcnet-hardware.txt | 142 Remember that you cannot connect two passive hubs together. The power loss
|
| /linux-4.4.14/Documentation/ |
| D | IRQ-affinity.txt | 32 6029 packets transmitted, 6027 packets received, 0% packet loss
49 2779 packets transmitted, 2777 packets received, 0% packet loss
|
| D | unaligned-memory-access.txt | 131 the extra instructions obviously cause a loss in performance compared to the
|
| D | sysrq.txt | 157 disks and will certainly lessen the chance of data loss and fscking. Note
|
| D | xillybus.txt | 321 the FPGA, and hence can't be sent. To prevent loss of data, these leftover
|
| D | CodingStyle | 151 (or almost empty) lines, without any loss of readability. Thus, as the
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-bus-fcoe | 35 fcf_dev_loss_tmo: Device loss timeout period (see below). Changing
104 dev_loss_tmo: The device loss timeout period for this FCF.
106 Notes: A device loss infrastructure similar to the FC Transport's
|
| /linux-4.4.14/tools/power/cpupower/bench/ |
| D | README-BENCH | 7 - Identify worst case performance loss when doing dynamic frequency
61 on full performance and you get the overall performance loss.
80 trigger of the cpufreq-bench, you will see no performance loss (compare with
|
| /linux-4.4.14/Documentation/ide/ |
| D | warm-plug-howto.txt | 18 results may be unpredictable and lead to data loss if you're unlucky
|
| /linux-4.4.14/net/sched/ |
| D | sch_netem.c | 83 u32 loss; member
288 return q->loss && q->loss >= get_crandom(&q->loss_cor); in loss_event()
910 q->loss = qopt->loss; in netem_change()
1031 qopt.loss = q->loss; in netem_dump()
|
| D | Kconfig | 200 Say Y if you want to emulate network delay, loss, and packet
|
| /linux-4.4.14/Documentation/devicetree/bindings/eeprom/ |
| D | eeprom.txt | 17 may result in data loss! If not specified, a safety value of
|
| /linux-4.4.14/Documentation/usb/ |
| D | ohci.txt | 25 transfers. Previously, using periods of one frame would risk data loss due
|
| D | ehci.txt | 70 of one frame without risking data loss due to interrupt processing costs.
|
| D | power-management.txt | 566 logically off, and may trigger the actual loss of VBUS to the port [3].
732 power session loss (suspend / port-power event). When
|
| /linux-4.4.14/Documentation/blockdev/drbd/ |
| D | drbd-connection-state-overview.dot | 16 label="{communication loss|{Timeout|BrokenPipe|NetworkFailure}}" ]
|
| /linux-4.4.14/arch/powerpc/boot/dts/fsl/ |
| D | b4420qds.dts | 29 * loss of use, data, or profits; or business interruption) however caused and
|
| D | b4420si-pre.dtsi | 29 * loss of use, data, or profits; or business interruption) however caused and
|
| D | p5040si-pre.dtsi | 29 * loss of use, data, or profits; or business interruption) however caused and
|
| D | b4420si-post.dtsi | 29 * loss of use, data, or profits; or business interruption) however caused and
|
| D | b4qds.dtsi | 29 * loss of use, data, or profits; or business interruption) however caused and
|
| D | p5040ds.dts | 29 * loss of use, data, or profits; or business interruption) however caused and
|
| D | b4si-post.dtsi | 29 * loss of use, data, or profits; or business interruption) however caused and
|
| D | p5040si-post.dtsi | 29 * loss of use, data, or profits; or business interruption) however caused and
|
| /linux-4.4.14/Documentation/filesystems/nfs/ |
| D | nfs.txt | 39 or loss of state during NFS reboot recovery or transparent state migration.
49 outstanding NFSv4 state has expired, to prevent loss of NFSv4 state.
|
| /linux-4.4.14/Documentation/arm64/ |
| D | legacy_instructions.txt | 28 performance, but at the loss of ability to gather runtime statistics
|
| /linux-4.4.14/net/ipv4/ |
| D | Kconfig | 525 window. TCP Vegas should provide less packet loss, but it is
552 distinguishing to circumvent the difficult judgment of the packet loss
554 loss packets.
563 algorithm, which uses a mixed loss/delay approach to compute the
565 internal, RTT and Reno fairness, resilience to link loss while
613 o Coexist with flows that use loss-based congestion control.
614 o Tolerate packet loss unrelated to congestion.
|
| /linux-4.4.14/drivers/atm/ |
| D | nicstarmac.copyright | 11 * loss of link, and correctly re-enable PHY when link is
|
| D | Kconfig | 209 loss, so if you have a 25Mbps NICStAR based ATM card you must say Y.
|
| /linux-4.4.14/fs/btrfs/ |
| D | Kconfig | 51 after a power-loss or kernel panic event the filesystem is
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | max16065 | 69 power loss, board resets, and/or Flash corruption. Worst case, your board may
|
| D | zl6100 | 83 to those registers are protected, this may result in power loss, board resets,
|
| /linux-4.4.14/Documentation/accounting/ |
| D | taskstats.txt | 164 loss. This possibility gets compounded when the taskstats structure gets
179 loss of data.
|
| /linux-4.4.14/Documentation/block/ |
| D | pr.txt | 17 a power loss and cover all connections in a multi path environment.
|
| /linux-4.4.14/drivers/scsi/mpt3sas/ |
| D | Kconfig | 26 # the risks and costs of program errors, damage to or loss of data,
|
| /linux-4.4.14/drivers/scsi/ufs/ |
| D | Kconfig | 29 # program errors, damage to or loss of data, programs or equipment,
|
| /linux-4.4.14/Documentation/scsi/ |
| D | dpti.txt | 13 * substitute goods or services; loss of use, data, or profits; or business
|
| D | libsas.txt | 286 PORTE_LINK_RESET_ERR -- timer expired, loss of signal, loss
|
| D | tmscsim.txt | 425 Tonneau) for intensively testing the driver (and even risking data loss
|
| D | ncr53c8xx.txt | 569 suffers no performance loss with this option since all IO is memory
|
| D | ChangeLog.lpfc | 680 device loss crashes.
|
| /linux-4.4.14/Documentation/vm/ |
| D | slub.txt | 289 - Slabs sorted by loss (up to -N <num> slabs, default 1)
312 - Slabs sorted by loss: FOO_STATS-slabs-by-loss.png
|
| /linux-4.4.14/Documentation/mmc/ |
| D | mmc-async-req.txt | 60 the performance loss. A way to optimize for this is to split the current
|
| /linux-4.4.14/drivers/misc/eeprom/ |
| D | Kconfig | 16 Unless you like data loss puzzles, always be sure that any chip
|
| /linux-4.4.14/Documentation/firmware_class/ |
| D | README | 127 themselves any more for dealing with firmware loss during system
|
| /linux-4.4.14/include/uapi/linux/ |
| D | pkt_sched.h | 538 __u32 loss; /* random packet loss (0=none ~0=100%) */ member
|
| /linux-4.4.14/Documentation/networking/caif/ |
| D | Linux-CAIF.txt | 172 The CAIF Protocol relies on a loss-less link layer without implementing
|
| /linux-4.4.14/Documentation/PCI/ |
| D | pcieaer-howto.txt | 100 intervention or any loss of data. These errors are detected and
171 software intervention or any loss of data. These errors do not
|
| /linux-4.4.14/Documentation/DocBook/ |
| D | 80211.xml.db | 150 API-ieee80211-beacon-loss
|
| /linux-4.4.14/arch/m68k/q40/ |
| D | README | 20 this is not known to have caused any data loss. On highly loaded systems
|
| /linux-4.4.14/Documentation/cpu-freq/ |
| D | user-guide.txt | 165 resulting in performance loss.
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | perf-top.txt | 177 between information loss and faster processing especially for
|
| D | perf-report.txt | 216 between information loss and faster processing especially for
|
| /linux-4.4.14/Documentation/dmaengine/ |
| D | client.txt | 177 This pauses activity on the DMA channel without data loss.
|
| /linux-4.4.14/Documentation/thermal/ |
| D | cpu-cooling-api.txt | 137 inactive periods without loss of context.
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | btrfs.txt | 155 filesystem corruption on a system crash or power loss.
|
| D | ext4.txt | 507 loss. The default is 2% or 4096 clusters,
|
| D | xfs-delayed-logging-design.txt | 127 being accumulated in memory. Hence the potential for loss of metadata on a
|
| D | proc.txt | 1589 from the truncating task's write_bytes, but there is information loss in doing
|
| /linux-4.4.14/fs/reiserfs/ |
| D | README | 115 loss for me. Mikhail Gilula was a brilliant innovator who also left
|
| /linux-4.4.14/drivers/media/tuners/ |
| D | mt2063.c | 1437 u32 loss = t1 % denom; in MT2063_fLO_FractionalTerm() local
1439 (((f_ref & 0x00003FFF) * num + (loss << 14)) + (denom / 2)) / denom; in MT2063_fLO_FractionalTerm()
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | compress_offload.txt | 200 - Packet-loss concealment is not supported. This would require an
|
| /linux-4.4.14/Documentation/power/ |
| D | devices.txt | 33 them without loss of data.
58 is cleanly powered down and reactivated without data or service loss.
|
| /linux-4.4.14/Documentation/isdn/ |
| D | README | 187 10 7 Carrier loss to disconnect time (ignored).
|
| D | INTERFACE | 740 packet-loss on receive or send. The field errcode of the cmd.parm
|
| /linux-4.4.14/Documentation/laptops/ |
| D | laptop-mode.txt | 771 …p mode and your battery interface $BATT_INFO is missing. This may lead to loss of data when the ba…
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 2.Process | 454 Individual developers are often, understandably, at a loss for a place to
|
| /linux-4.4.14/Documentation/nvdimm/ |
| D | nvdimm.txt | 116 are expected to be durable after a system power loss. Now, the NFIT
|
| /linux-4.4.14/Documentation/cdrom/ |
| D | cdrom-standard.tex | 430 errors at these high speeds, reducing the speed can prevent data loss
|
| /linux-4.4.14/lib/ |
| D | Kconfig.debug | 141 resolve line numbers there is no loss. Advantage is that
|
| /linux-4.4.14/drivers/scsi/ |
| D | Kconfig | 953 now and then to avoid data loss. This will be done if you say Y
|