-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dpdk+netwrap+nginx can be ok? #225
Comments
When using ODP-DPDK you have to first bind the NIC ports to DPDK. You can follow instructions in https://github.com/OpenDataPlane/odp-dpdk/blob/master/platform/linux-dpdk/README : After this has been done you have to change the interface name to port index (e.g. eth1 -> 0) in |
ok, i have bind the nic port to dpdk, and also find the issue to modify eth1 -> 0 in ofp_netwrap.sh
|
The |
nginx log level is setted to be debug and no warning or error log;
and it works! The |
Makes sense. In daemon mode the nginx master process exits, which triggers the netwrap destructor. |
And it actually worked?? Last time I checked, netwrap was not working with dpdk... was something about dpdk using epoll inside. Basically, I was using odp + linux-generic
|
actually it has not worked yet, |
does netwrap epoll support both level-triggerded and edge-triggered ? |
Is not about netwrap epoll support but is more about ofp_epoll implementation: only EPOLLIN (OFP_EPOLLIN) event type can be set and only Level Triggered behaviour is supported. |
i want to run the latest nginx with netwrap which is implemented with odp-dpdk, i tried
1、download dpdk stable 17.11;
2、download odp-dpdk-1.19.0.2_DPDK_17.11;
3、download ofp-3.0.0;
before compile with scripts/devbuild_ofp_odp_dpdk.sh, i modify the ofp ./configure,below:
./configure --with-odp=$REPOS/odp-dpdk/install --enable-cunit --prefix=$REPOS/install/ --with-config-flv=netwrap-webserver --enable-sp=no
and something is wrong:
1、libofp.so.0.0.0 not found,i try to change to libofp.so.3.0.0 in ofp_netwrap.sh;
2、after that:
is something i did wrong?thx
The text was updated successfully, but these errors were encountered: