Skip to content

Conversation

sugchand
Copy link
Contributor

Adding a self-guide for configuring native userspace tunneling in OVS
with/without DPDK ports. This document also provides necessary debugging
commands to identify userspace tunneling issues in OVS.

Signed-off-by: Sugesh Chandran sugesh.chandran@intel.com

@ddiproietto
Copy link
Contributor

Thanks again for the pull request,

I have further comments:

  • The script dpdk_nic_bind.py should be invoked before starting OVS, otherwise it will be impossible to see the interface from the daemon. Since this is a step-by-step guide I think we should list the steps in the appropriate order
  • KNI refers to a DPDK-specific way of accessing an internal port. The steps listed in the page to access eth1 do not involve KNI at all (they use an AF_PACKET socket on linux and the pcap library on BSD).

Other than this I think the page is a great addition to the website.

Would you mind fixing that and resubmitting?

Thanks

@sugchand sugchand closed this Nov 2, 2015
@sugchand
Copy link
Contributor Author

sugchand commented Nov 2, 2015

Thank you for your time to review the document.
I have incorporated your comments and initiated a new pull request as below
#25
please review the same.

@sugchand
Copy link
Contributor Author

sugchand commented Nov 2, 2015

Hi Daniele,
I have incorporated all your comments and created a new pull request as below
#25
Can you please review the same??

Regards
_Sugesh

From: ddiproietto [mailto:notifications@github.com]
Sent: Friday, October 30, 2015 5:11 PM
To: openvswitch/openvswitch.github.io
Cc: Chandran, Sugesh
Subject: Re: [openvswitch.github.io] Detailed documentation for configuring native userspace-tunneling in OVS (#24)

Thanks again for the pull request,

I have further comments:

  • The script dpdk_nic_bind.py should be invoked before starting OVS, otherwise it will be impossible to see the interface from the daemon. Since this is a step-by-step guide I think we should list the steps in the appropriate order
  • KNI refers to a DPDK-specific way of accessing an internal port. The steps listed in the page to access eth1 do not involve KNI at all (they use an AF_PACKET socket on linux and the pcap library on BSD).

Other than this I think the page is a great addition to the website.

Would you mind fixing that and resubmitting?

Thanks


Reply to this email directly or view it on GitHubhttps://github.com//pull/24#issuecomment-152589284.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants