| /linux-4.4.14/drivers/net/wireless/iwlwifi/dvm/ |
| D | led.c | 56 { .throughput = 0, .blink_time = 334 },
57 { .throughput = 1 * 1024 - 1, .blink_time = 260 },
58 { .throughput = 5 * 1024 - 1, .blink_time = 220 },
59 { .throughput = 10 * 1024 - 1, .blink_time = 190 },
60 { .throughput = 20 * 1024 - 1, .blink_time = 170 },
61 { .throughput = 50 * 1024 - 1, .blink_time = 150 },
62 { .throughput = 70 * 1024 - 1, .blink_time = 130 },
63 { .throughput = 100 * 1024 - 1, .blink_time = 110 },
64 { .throughput = 200 * 1024 - 1, .blink_time = 80 },
65 { .throughput = 300 * 1024 - 1, .blink_time = 50 },
|
| /linux-4.4.14/net/x25/ |
| D | x25_facilities.c | 108 facilities->throughput = p[1]; in x25_parse_facilities()
215 if (facilities->throughput && (facil_mask & X25_MASK_THROUGHPUT)) { in x25_create_facilities()
217 *p++ = facilities->throughput; in x25_create_facilities()
296 if (theirs.throughput) { in x25_negotiate_facilities()
297 int theirs_in = theirs.throughput & 0x0f; in x25_negotiate_facilities()
298 int theirs_out = theirs.throughput & 0xf0; in x25_negotiate_facilities()
299 int ours_in = ours->throughput & 0x0f; in x25_negotiate_facilities()
300 int ours_out = ours->throughput & 0xf0; in x25_negotiate_facilities()
303 new->throughput = (new->throughput & 0xf0) | theirs_in; in x25_negotiate_facilities()
308 new->throughput = (new->throughput & 0x0f) | theirs_out; in x25_negotiate_facilities()
|
| D | af_x25.c | 582 x25->facilities.throughput = 0; /* by default don't negotiate in x25_create()
1457 if (facilities.throughput) { in x25_ioctl()
1458 int out = facilities.throughput & 0xf0; in x25_ioctl()
1459 int in = facilities.throughput & 0x0f; in x25_ioctl()
1461 facilities.throughput |= in x25_ioctl()
1466 facilities.throughput |= in x25_ioctl()
|
| /linux-4.4.14/drivers/gpu/drm/amd/amdgpu/ |
| D | amdgpu_benchmark.c | 65 unsigned int throughput = (n * (size >> 10)) / time; in amdgpu_benchmark_log_results() local
69 throughput * 8, throughput); in amdgpu_benchmark_log_results()
|
| /linux-4.4.14/drivers/gpu/drm/radeon/ |
| D | radeon_benchmark.c | 80 unsigned int throughput = (n * (size >> 10)) / time; in radeon_benchmark_log_results() local
84 throughput * 8, throughput); in radeon_benchmark_log_results()
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | dm-service-time.txt | 10 The performance value is a relative throughput value among all paths
20 <relative_throughput>: The relative throughput value of the path
32 <relative_throughput>: The relative throughput value of the path
69 and sda has an average throughput 1GB/s and sdb has 4GB/s,
|
| D | striped.txt | 7 potentially provide improved I/O throughput by utilizing several physical
|
| /linux-4.4.14/kernel/ |
| D | Kconfig.preempt | 10 throughput. It will still provide good latencies most of the
26 at the cost of slightly lower throughput.
48 system is under load, at the cost of slightly lower throughput
|
| /linux-4.4.14/drivers/net/wireless/ath/ath9k/ |
| D | htc_drv_init.c | 51 { .throughput = 0 * 1024, .blink_time = 334 },
52 { .throughput = 1 * 1024, .blink_time = 260 },
53 { .throughput = 5 * 1024, .blink_time = 220 },
54 { .throughput = 10 * 1024, .blink_time = 190 },
55 { .throughput = 20 * 1024, .blink_time = 170 },
56 { .throughput = 50 * 1024, .blink_time = 150 },
57 { .throughput = 70 * 1024, .blink_time = 130 },
58 { .throughput = 100 * 1024, .blink_time = 110 },
59 { .throughput = 200 * 1024, .blink_time = 80 },
60 { .throughput = 300 * 1024, .blink_time = 50 },
|
| D | init.c | 80 { .throughput = 0 * 1024, .blink_time = 334 },
81 { .throughput = 1 * 1024, .blink_time = 260 },
82 { .throughput = 5 * 1024, .blink_time = 220 },
83 { .throughput = 10 * 1024, .blink_time = 190 },
84 { .throughput = 20 * 1024, .blink_time = 170 },
85 { .throughput = 50 * 1024, .blink_time = 150 },
86 { .throughput = 70 * 1024, .blink_time = 130 },
87 { .throughput = 100 * 1024, .blink_time = 110 },
88 { .throughput = 200 * 1024, .blink_time = 80 },
89 { .throughput = 300 * 1024, .blink_time = 50 },
|
| /linux-4.4.14/Documentation/ide/ |
| D | ide-tape.txt | 32 Maximal throughput with minimal bus load will usually be achieved in the
49 In order to maximize bus throughput, we currently use the DSC
64 a method by which we can achieve higher throughput when
|
| D | ChangeLog.ide-tape.1995-2002 | 82 * throughput can potentially reach the maximum
83 * tape supported throughput, regardless of the
95 * higher tape throughput.
131 * interactive response and high system throughput.
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-driver-xen-blkfront | 8 is 32 - higher value means more potential throughput but more
|
| D | sysfs-block | 144 throughput is desired. If no optimal I/O size is
|
| /linux-4.4.14/include/uapi/linux/ |
| D | x25.h | 105 unsigned int throughput; member
|
| D | wireless.h | 971 __u32 throughput; /* To give an idea... */ member
|
| /linux-4.4.14/Documentation/block/ |
| D | deadline-iosched.txt | 42 throughput. When low latency is the primary concern, smaller is better (where
44 generally improves throughput, at the cost of latency variation.
|
| D | cfq-iosched.txt | 24 seeks and see improved throughput.
27 level and one should see an overall improved throughput on faster storage
37 throughput and acceptable latencies.
79 multiple queues in the group at the same time and achieve higher throughput
89 for the system. This favors fairness over throughput. Disabling low
100 then to meet the latency constraints, throughput may decrease because of less
106 throughput and read latency.
|
| D | switching-sched.txt | 20 can improve that device's throughput).
|
| D | biodoc.txt | 896 throughput or whatever purpose. As the plural form indicates, there are
986 i. improved throughput
|
| /linux-4.4.14/drivers/atm/ |
| D | Kconfig | 67 In order to obtain good throughput, the ENI NIC can transfer
80 resulting throughput is lower than when using only the largest
83 Also, sometimes larger bursts lead to lower throughput, e.g. on an
107 may or may not improve throughput.
115 are also set may or may not improve throughput.
138 improve throughput.
146 8W are also set may or may not improve throughput.
|
| /linux-4.4.14/Documentation/arm/OMAP/ |
| D | omap_pm | 7 throughput constraints to the kernel power management code.
20 latency and throughput, rather than units which are specific to OMAP
43 4. Set the minimum bus throughput needed by a device:
|
| /linux-4.4.14/drivers/staging/fbtft/ |
| D | fbtft-core.c | 350 long fps, throughput; in fbtft_update_display() local
402 throughput = ktime_us_delta(ts_end, ts_start); in fbtft_update_display()
403 throughput = throughput ? (len * 1000) / throughput : 0; in fbtft_update_display()
404 throughput = throughput * 1000 / 1024; in fbtft_update_display()
408 throughput, fps); in fbtft_update_display()
|
| /linux-4.4.14/Documentation/networking/ |
| D | e1000e.txt | 103 for bulk throughput traffic.
114 the overall throughput, we recommend that you load the driver as
134 extra latency to frame reception and can end up decreasing the throughput
155 along with RxIntDelay, may improve traffic throughput in specific network
178 along with TxIntDelay, may improve traffic throughput in specific
|
| D | e1000.txt | 135 for bulk throughput traffic.
156 the overall throughput, we recommend that you load the driver as
195 extra latency to frame reception and can end up decreasing the throughput
217 along with RxIntDelay, may improve traffic throughput in specific network
297 along with TxIntDelay, may improve traffic throughput in specific
414 Degradation in throughput performance may be observed in some Jumbo frames
|
| D | ixgb.txt | 148 decreasing the throughput of TCP traffic. If the system is reporting
170 very likely limit the total available throughput artificially. There is a set
213 # these are just suggested values that worked well to increase throughput in
373 Degradation in throughput performance may be observed in some Jumbo frames
|
| D | netlink_mmap.txt | 8 Memory mapped netlink I/O can be used to increase throughput and decrease
10 require high throughput, these are mainly the netfilter subsystems
|
| D | ieee802154.txt | 119 with a link throughput of 250 kbps or less. The 6LoWPAN adaptation format
|
| D | vortex.txt | 210 decrease in throughput for send(). There is no effect upon receive
315 10baseT LAN plugged into a switched 100baseT LAN, the throughput
|
| D | ip-sysctl.txt | 340 latency as opposed to higher throughput. By default, this
341 option is not set meaning that higher throughput is preferred.
398 match the size required by the path for full throughput. Enabled by
618 is applied to conservatively probe for bigger throughput.
840 reduces overall throughput, in such case you should disable it.
|
| D | bonding.txt | 737 higher throughput than another.
2130 could provide higher throughput.
2232 throughput depends upon the application and network environment. The
2310 worth of throughput. This comes at a cost, however: the
2437 Multiple switches may be utilized to optimize for throughput
|
| /linux-4.4.14/net/dccp/ccids/ |
| D | Kconfig | 23 throughput over time compared with TCP, which makes CCID-3 more
|
| /linux-4.4.14/net/mac80211/ |
| D | led.c | 271 if (tpt_trig->blink_table[i].throughput < 0 || in tpt_trig_timer()
272 tpt > tpt_trig->blink_table[i].throughput) { in tpt_trig_timer()
|
| /linux-4.4.14/net/batman-adv/ |
| D | Kconfig | 45 increase the overall network throughput by fusing multiple
|
| /linux-4.4.14/Documentation/usb/ |
| D | ehci.txt | 141 USB 2.0 throughput is gated by two main factors: how fast the host
144 but aggregate throughput is also affected by issues like delays between
148 Bulk transfers are most often used where throughput is an issue. It's
|
| /linux-4.4.14/Documentation/mmc/ |
| D | mmc-async-req.txt | 20 The increase in throughput is proportional to the time it takes to
|
| /linux-4.4.14/Documentation/mips/ |
| D | AU1xxx_IDE.README | 95 high IDE to USB throughput.
|
| /linux-4.4.14/drivers/net/wireless/iwlegacy/ |
| D | common.c | 456 {.throughput = 0, .blink_time = 334},
457 {.throughput = 1 * 1024 - 1, .blink_time = 260},
458 {.throughput = 5 * 1024 - 1, .blink_time = 220},
459 {.throughput = 10 * 1024 - 1, .blink_time = 190},
460 {.throughput = 20 * 1024 - 1, .blink_time = 170},
461 {.throughput = 50 * 1024 - 1, .blink_time = 150},
462 {.throughput = 70 * 1024 - 1, .blink_time = 130},
463 {.throughput = 100 * 1024 - 1, .blink_time = 110},
464 {.throughput = 200 * 1024 - 1, .blink_time = 80},
465 {.throughput = 300 * 1024 - 1, .blink_time = 50},
|
| /linux-4.4.14/tools/power/cpupower/bench/ |
| D | README-BENCH | 19 throughput is, the worse the power savings will be, but the first should
|
| /linux-4.4.14/drivers/staging/rtl8192u/ |
| D | r8192U_wx.c | 208 __u32 throughput; /* To give an idea... */ member
249 range->throughput = 5 * 1000 * 1000; in rtl8180_wx_get_range()
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | serial-u16550.txt | 71 the MIDI Outs to act independently at double the aggregate throughput of M/B,
|
| D | hdspm.txt | 23 allocated. So also the throughput of the PCI system can be
|
| D | ALSA-Configuration.txt | 1805 This magic number seems to give pretty optimal throughput
|
| /linux-4.4.14/net/ipv4/ |
| D | Kconfig | 486 wired networks and throughput over wireless links.
551 throughput over wireless networks. TCP Veno makes use of state
578 throughput and maintain fairness.
592 - High throughput (continuous data updates, large file transfers) with
|
| /linux-4.4.14/drivers/net/wireless/b43/ |
| D | Kconfig | 135 bool "Support for HT-PHY (high throughput 802.11n) devices"
|
| /linux-4.4.14/drivers/net/wireless/iwlwifi/ |
| D | Kconfig | 98 expected throughput due to those APs not enabling aggregation
|
| /linux-4.4.14/drivers/isdn/i4l/ |
| D | Kconfig | 33 With synchronous PPP enabled, it is possible to increase throughput
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | blkio-controller.txt | 360 able to driver higher queue depth and achieve better throughput. That also
373 One can experience an overall throughput drop if you have created multiple
376 on individual groups and throughput should improve.
|
| /linux-4.4.14/Documentation/scsi/ |
| D | aha152x.txt | 13 less polling loops), has slightly higher throughput (at
|
| D | st.txt | 249 -b option) may have had good throughput but this is not true any more with
|
| D | sym53c8xx_2.txt | 605 Synchronous data transfers increases throughput of fast devices like
|
| D | ncr53c8xx.txt | 1264 Synchronous data transfers increases throughput of fast devices like
|
| /linux-4.4.14/drivers/staging/rtl8192e/rtl8192e/ |
| D | rtl_wx.c | 298 __u32 throughput; /* To give an idea... */ member
331 range->throughput = 130 * 1000 * 1000; in _rtl92e_wx_get_range()
|
| /linux-4.4.14/Documentation/hid/ |
| D | hid-transport.txt | 100 not send via intr, except if high throughput is required.
291 which require high throughput for outgoing requests on the intr channel. This
|
| /linux-4.4.14/Documentation/networking/caif/ |
| D | spi_porting.txt | 83 In order to optimize throughput, a number of SPI padding options are provided.
|
| /linux-4.4.14/Documentation/ |
| D | stable_api_nonsense.txt | 110 increased the throughput of all USB drivers such that we are now
|
| D | kernel-parameters.txt | 3630 improve throughput, but will also increase the
|
| /linux-4.4.14/Documentation/power/ |
| D | pm_qos_interface.txt | 16 * throughput: kbs (kilo bit / sec)
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | ext4.txt | 282 huge throughput win, we wait for a small amount
301 this parameter may improve the throughput of
|
| D | xfs-delayed-logging-design.txt | 72 minimise the impact of the log IO on transaction throughput.
74 The limitation on asynchronous transaction throughput is the number and size of
|
| /linux-4.4.14/Documentation/target/ |
| D | tcmu-design.txt | 77 - Good performance: high throughput, low latency
|
| /linux-4.4.14/drivers/md/ |
| D | Kconfig | 69 the throughput rate if the partitions reside on distinct disks.
|
| /linux-4.4.14/include/net/ |
| D | mac80211.h | 3564 int throughput; member
|
| /linux-4.4.14/drivers/net/wireless/ |
| D | wl3501_cs.c | 1513 range->throughput = 2 * 1000 * 1000; /* ~2 Mb/s */ in wl3501_get_range()
|
| D | ray_cs.c | 1336 range->throughput = 1.1 * 1000 * 1000; /* Put the right number here */ in ray_get_range()
|
| D | airo.c | 6947 range->throughput = 5000 * 1000; in airo_get_range()
6949 range->throughput = 1500 * 1000; in airo_get_range()
|
| /linux-4.4.14/drivers/mmc/host/ |
| D | Kconfig | 708 sent to VUB300 chip in order to achieve better data throughput.
|
| /linux-4.4.14/drivers/ide/ |
| D | Kconfig | 341 Linux. This may slow disk throughput by a few percent, but at least
|
| /linux-4.4.14/drivers/staging/rtl8712/ |
| D | rtl871x_ioctl_linux.c | 884 range->throughput = 5 * 1000 * 1000; in r8711_wx_get_range()
|
| /linux-4.4.14/drivers/staging/rtl8188eu/os_dep/ |
| D | ioctl_linux.c | 883 range->throughput = 5 * 1000 * 1000; in rtw_wx_get_range()
|
| /linux-4.4.14/crypto/ |
| D | Kconfig | 682 better throughput. It should not be enabled by default but
|
| /linux-4.4.14/drivers/net/wireless/hostap/ |
| D | hostap_ioctl.c | 1050 range->throughput = over2 ? 5500000 : 1500000; in prism2_ioctl_giwrange()
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | vivid.txt | 1127 - Use per-queue locks and/or per-device locks to improve throughput
|
| /linux-4.4.14/arch/arm/ |
| D | Kconfig | 1774 memory write throughput than a sequence of individual 32bit stores.
|
| /linux-4.4.14/init/ |
| D | Kconfig | 768 RCU-callback invocation, thus potentially degrading throughput.
|
| /linux-4.4.14/drivers/net/wireless/ipw2x00/ |
| D | ipw2100.c | 6805 range->throughput = 5 * 1000 * 1000; in ipw2100_wx_get_range()
|
| D | ipw2200.c | 8852 range->throughput = 27 * 1000 * 1000; in ipw_wx_get_range()
|