| /linux-3.4.99/drivers/net/wireless/iwlwifi/ |
| D | iwl-led.c | 59 { .throughput = 0, .blink_time = 334 },
60 { .throughput = 1 * 1024 - 1, .blink_time = 260 },
61 { .throughput = 5 * 1024 - 1, .blink_time = 220 },
62 { .throughput = 10 * 1024 - 1, .blink_time = 190 },
63 { .throughput = 20 * 1024 - 1, .blink_time = 170 },
64 { .throughput = 50 * 1024 - 1, .blink_time = 150 },
65 { .throughput = 70 * 1024 - 1, .blink_time = 130 },
66 { .throughput = 100 * 1024 - 1, .blink_time = 110 },
67 { .throughput = 200 * 1024 - 1, .blink_time = 80 },
68 { .throughput = 300 * 1024 - 1, .blink_time = 50 },
|
| /linux-3.4.99/net/x25/ |
| D | x25_facilities.c | 106 facilities->throughput = p[1]; in x25_parse_facilities()
209 if (facilities->throughput && (facil_mask & X25_MASK_THROUGHPUT)) { in x25_create_facilities()
211 *p++ = facilities->throughput; in x25_create_facilities()
289 if (theirs.throughput) { in x25_negotiate_facilities()
290 int theirs_in = theirs.throughput & 0x0f; in x25_negotiate_facilities()
291 int theirs_out = theirs.throughput & 0xf0; in x25_negotiate_facilities()
292 int ours_in = ours->throughput & 0x0f; in x25_negotiate_facilities()
293 int ours_out = ours->throughput & 0xf0; in x25_negotiate_facilities()
296 new->throughput = (new->throughput & 0xf0) | theirs_in; in x25_negotiate_facilities()
301 new->throughput = (new->throughput & 0x0f) | theirs_out; in x25_negotiate_facilities()
|
| D | af_x25.c | 583 x25->facilities.throughput = 0; /* by default don't negotiate in x25_create()
1460 if (facilities.throughput) { in x25_ioctl()
1461 int out = facilities.throughput & 0xf0; in x25_ioctl()
1462 int in = facilities.throughput & 0x0f; in x25_ioctl()
1464 facilities.throughput |= in x25_ioctl()
1469 facilities.throughput |= in x25_ioctl()
|
| /linux-3.4.99/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-3.4.99/drivers/gpu/drm/radeon/ |
| D | radeon_benchmark.c | 89 unsigned int throughput = (n * (size >> 10)) / time; in radeon_benchmark_log_results() local
93 throughput * 8, throughput); in radeon_benchmark_log_results()
|
| /linux-3.4.99/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-3.4.99/drivers/net/wireless/ath/ath9k/ |
| D | htc_drv_init.c | 120 { .throughput = 0 * 1024, .blink_time = 334 },
121 { .throughput = 1 * 1024, .blink_time = 260 },
122 { .throughput = 5 * 1024, .blink_time = 220 },
123 { .throughput = 10 * 1024, .blink_time = 190 },
124 { .throughput = 20 * 1024, .blink_time = 170 },
125 { .throughput = 50 * 1024, .blink_time = 150 },
126 { .throughput = 70 * 1024, .blink_time = 130 },
127 { .throughput = 100 * 1024, .blink_time = 110 },
128 { .throughput = 200 * 1024, .blink_time = 80 },
129 { .throughput = 300 * 1024, .blink_time = 50 },
|
| D | init.c | 148 { .throughput = 0 * 1024, .blink_time = 334 },
149 { .throughput = 1 * 1024, .blink_time = 260 },
150 { .throughput = 5 * 1024, .blink_time = 220 },
151 { .throughput = 10 * 1024, .blink_time = 190 },
152 { .throughput = 20 * 1024, .blink_time = 170 },
153 { .throughput = 50 * 1024, .blink_time = 150 },
154 { .throughput = 70 * 1024, .blink_time = 130 },
155 { .throughput = 100 * 1024, .blink_time = 110 },
156 { .throughput = 200 * 1024, .blink_time = 80 },
157 { .throughput = 300 * 1024, .blink_time = 50 },
|
| /linux-3.4.99/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-3.4.99/include/linux/ |
| D | x25.h | 105 unsigned int throughput; member
|
| /linux-3.4.99/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 | 13 seeks and see improved throughput.
16 level and one should see an overall improved throughput on faster storage
26 throughput and acceptable latencies.
|
| D | switching-sched.txt | 20 can improve that device's throughput).
|
| /linux-3.4.99/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-3.4.99/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-3.4.99/net/mac80211/ |
| D | led.c | 205 if (tpt_trig->blink_table[i].throughput < 0 || in tpt_trig_timer()
206 tpt > tpt_trig->blink_table[i].throughput) { in tpt_trig_timer()
|
| /linux-3.4.99/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
|
| /linux-3.4.99/net/dccp/ccids/ |
| D | Kconfig | 24 throughput over time compared with TCP, which makes CCID-3 more
|
| /linux-3.4.99/Documentation/video4linux/ |
| D | se401.txt | 46 order to increase the throughput (and thus framerate).
|
| /linux-3.4.99/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-3.4.99/Documentation/mips/ |
| D | AU1xxx_IDE.README | 95 high IDE to USB throughput.
|