diff options
| author |   Hanoh Haim <hhaim@cisco.com> | 2017-02-07 17:27:39 +0200 |
|---|---|---|
| committer | Hanoh Haim <hhaim@cisco.com> | 2017-02-07 17:27:39 +0200 |
| commit | a92ac3fec49a04dcfaa690aeeaec98e23216262d (patch) | |
| tree | 93aa30e866b6f2e5a1dadbfd8e50656710264060 /doc | |
| parent | ca53bd59481c69447b3090e5c0596f45bdf83361 (diff) | |
doc update sr_iov section
Signed-off-by: Hanoh Haim <hhaim@cisco.com>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/images/sr_iov_trex.png | bin | 0 -> 24640 bytes | |||
| -rw-r--r-- | doc/images/sr_iov_vswitch.png | bin | 0 -> 23122 bytes | |||
| -rwxr-xr-x | doc/trex_book.asciidoc | 16 |
3 files changed, 16 insertions, 0 deletions
diff --git a/doc/images/sr_iov_trex.png b/doc/images/sr_iov_trex.png Binary files differnew file mode 100644 index 00000000..dba6dfa2 --- /dev/null +++ b/doc/images/sr_iov_trex.png diff --git a/doc/images/sr_iov_vswitch.png b/doc/images/sr_iov_vswitch.png Binary files differnew file mode 100644 index 00000000..472e3c09 --- /dev/null +++ b/doc/images/sr_iov_vswitch.png diff --git a/doc/trex_book.asciidoc b/doc/trex_book.asciidoc index 3c72e964..390408d1 100755 --- a/doc/trex_book.asciidoc +++ b/doc/trex_book.asciidoc @@ -2146,6 +2146,22 @@ sudo arp -s 172.168.0.100 <TRex side the NICs are not visible to ifconfig, run: ---- === Configure Linux to use VF on Intel X710 and 82599 NICs + +TRex supports paravirtualized interfaces such as VMXNET3/virtio/E1000 however when connected to a vSwitch, the vSwitch limits the performance. VPP or OVS-DPDK can improve the performance but require more software resources to handle the rate. +SR-IOV can accelerate the performance and reduce CPU resource usage as well as latency by utilizing NIC hardware switch capability (the switching is done by hardware). +TRex version 2.15 now includes SR-IOV support for XL710 and X710. +The following diagram compares between vSwitch and SR-IOV. + +image:images/sr_iov_vswitch.png[title="vSwitch_main",width=850] + +One use case which shows the performance gain that can be acheived by using SR-IOV is when a user wants to create a pool of TRex VMs that tests a pool of virtual DUTs (e.g. ASAv,CSR etc.) +When using newly supported SR-IOV, compute, storage and networking resources can be controlled dynamically (e.g by using OpenStack) + +image:images/sr_iov_trex.png[title="vSwitch_main",width=850] + +The above diagram is an example of one server with two NICS. TRex VMs can be allocated on one NIC while the DUTs can be allocated on another. + + Following are some links we used and lessons we learned while putting up an environment for testing TRex with VF interfaces (using SR-IOV). This is by no means a full toturial of VF usage, and different Linux distributions might need slightly different handling. |
