-
Notifications
You must be signed in to change notification settings - Fork 8
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
Add systemd for binding dpdk port after reboot #212
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #212 +/- ##
========================================
Coverage 78.16% 78.16%
========================================
Files 49 49
Lines 2469 2469
========================================
Hits 1930 1930
Misses 416 416
Partials 123 123 Continue to review full report at Codecov.
|
加一下註解 |
30d4cff
to
e88e4cc
Compare
會再繼續研究用 systemd |
developers/Vagrantfile
Outdated
sudo ${DPDK_DIR}/usertools/dpdk-devbind.py --bind=igb_uio ${NET_IF_NAME} | ||
# Note that this NIC setup will binding dpdk port after reboot | ||
echo 'export IFDRV=igb_uio' | sudo tee -a /root/.bashrc | ||
echo 'export IFnum=enp0s8' | sudo tee -a /root/.bashrc |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IFDRV
跟 IFnum
其實沒用到?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
喔 對的
這就拿掉他們
f3ca6d6
to
3702032
Compare
@@ -0,0 +1,11 @@ | |||
[Unit] | |||
Description=Binding dpdk port after reboot | |||
After=network-pre.target multi-user.target |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
multi-user.target 為什麼要在 dpdkbind.service 之後呀?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
恩~這邊沒有特別研究。
不過我把 network-pre.target
拿掉了
因為原本的寫法, reboot 後,不能 vagrant ssh 。拿掉就可以了~
然後重新進到 VM 中,也有看到 dpdk 的 port 有綁定了。
3702032
to
e5015bc
Compare
Remove rc.local config and use dpdkbind systemd to bind dpdk port after reboot
02d5dc8
to
9c63b2a
Compare
這個 PR 測過是 OK 的。 |
021f646
to
f7b5ab3
Compare
developers/Vagrantfile
Outdated
sudo ifconfig ${NET_IF_NAME} down | ||
sudo ${DPDK_DIR}/usertools/dpdk-devbind.py --bind=igb_uio ${NET_IF_NAME} | ||
# Note that this NIC setup will binding dpdk port after reboot | ||
echo 'NET_IF_NAME=enp0s18' | sudo tee -a /etc/default/dpdkbind |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
echo 'NET_IF_NAME='${NET_IF_NAME} | sudo tee -a /etc/default/dpdkbind
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
f7b5ab3
to
96a70be
Compare
- Add dpdkbind.service for systemd - Update kernel module from uio to igb_uio cc linkernetworks/vortex#212
- Add dpdkbind.service for systemd - Update kernel module from uio to igb_uio cc linkernetworks/vortex#212
- Add dpdkbind.service for systemd - Update kernel module from uio to igb_uio cc linkernetworks/vortex#212
- Add dpdkbind.service for systemd - Update kernel module from uio to igb_uio cc linkernetworks/vortex#212
- Add dpdkbind.service for systemd - Update kernel module from uio to igb_uio cc linkernetworks/vortex#212
- Add dpdkbind.service for systemd - Update kernel module from uio to igb_uio cc linkernetworks/vortex#212
- Add dpdkbind.service for systemd - Update kernel module from uio to igb_uio cc linkernetworks/vortex#212
- Add dpdkbind.service for systemd - Update kernel module from uio to igb_uio cc linkernetworks/vortex#212
No description provided.