diff options
| author | Derek Kozel <derek.kozel@ettus.com> | 2016-10-20 19:50:00 -0700 |
|---|---|---|
| committer | mbr0wn <martin.braun@ettus.com> | 2016-10-21 10:05:23 -0700 |
| commit | 2a0e0612dcc9a477e690addae3fd8b42ed301f26 (patch) | |
| tree | 43eb9c9e86bc6d6ba4071b3eac3027bd9adafb94 /host/docs/transport.dox | |
| parent | 9b215d85b7ae09b253839f93284a637ebc3385c3 (diff) | |
| download | uhd-2a0e0612dcc9a477e690addae3fd8b42ed301f26.tar.gz uhd-2a0e0612dcc9a477e690addae3fd8b42ed301f26.tar.bz2 uhd-2a0e0612dcc9a477e690addae3fd8b42ed301f26.zip | |
Docs: Minor housekeeping
Diffstat (limited to 'host/docs/transport.dox')
| -rw-r--r-- | host/docs/transport.dox | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/host/docs/transport.dox b/host/docs/transport.dox index ab163341d..2cedcccb2 100644 --- a/host/docs/transport.dox +++ b/host/docs/transport.dox @@ -8,7 +8,7 @@ A transport is the layer between the packet interface and a device IO interface. The advanced user can pass optional parameters into the underlying transport layer through the device address. These optional parameters control how the transport object allocates memory, resizes -kernel buffers, spawns threads, etc. When not spcified, the transport +kernel buffers, spawns threads, etc. When not specified, the transport layer will use values for these parameters that are known to perform well on a variety of systems. The transport parameters are defined below for the various transports in the UHD software: @@ -29,7 +29,7 @@ see uhd::stream_args_t::args): - `num_recv_frames:` The number of receive buffers to allocate - `send_frame_size:` The size of a single send buffer in bytes - `num_send_frames:` The number of send buffers to allocate -- `recv_buff_fullness:` The targetted fullness factor of the the buffer (typically around 90%) +- `recv_buff_fullness:` The targeted fullness factor of the the buffer (typically around 90%) <b>Notes:</b> - `num_recv_frames` does not affect performance. @@ -78,8 +78,8 @@ proportional to the sample rate. Therefore, to improve receive latency, configure the transport for a smaller frame size. <b>Note2:</b> For overall latency improvements, look for "Interrupt -Coalescing" settings for your OS and ethernet chipset. It seems the -Intel ethernet chipsets offer fine-grained control in Linux. Also, +Coalescing" settings for your OS and Ethernet chipset. It seems the +Intel Ethernet chipsets offer fine-grained control in Linux. Also, consult: - <http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.prftungd/doc/prftungd/interrupt_coal.htm> |