-
Notifications
You must be signed in to change notification settings - Fork 321
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
FromDPDKDevice() doesn't set_mac_header #352
FromDPDKDevice() doesn't set_mac_header #352
Comments
Hi, We may want to add also the network and transport headers that are directly given by the NIC when possible. I'll look at that in a second time. Regarding the packet type anno, I remember copying what was done for the Netmap mode. I'm not sure if the behaviour of that should change. Any idea? I'm not sure where it is used and why. |
Thanks for the reply Tom, I will send a PR later today or tomorrow the latest. Network and transport headers that are directly given by the NIC would be great, thanks for looking into that later! I'm not sure about the packet type either, I'm fairly new to the codebase :) Will try to look into that a little. Keep up the good work! |
FromDPDKDevice now calls set_mac_header, like other sources. This closes kohler#352.
FromDPDKDevice now calls set_mac_header, like other sources. This closes kohler/click#352
Hi Tom, submitted the same change in click and fastclick also (actually I'm using fastclick, I only reported in click since the issue came from the parent project), since I don't know which one is easier for you. Feel free to reject one of the PRs, or however you like to do it. It's probably the simplest patch ever, but as Deep Thought said in the HGTG, at least it's very well tested. Keep up the good work, and thanks! :) K. |
Thanks ! |
FromDPDKDevice now calls set_mac_header, like other sources. This closes kohler#352.
Damn, I'm new to this. Ok, will do in a moment :) |
Hi Click team,
first of all, thanks for the great software.
While developing a custom Element, I've noticed that while most source elements set the originated packets' mac header address with something along the lines of
p->set_mac_header(p->data());
,FromDPDKDevice
doesn't.Is there a rationale behind this that I don't see (performance, memory, etc), or is it merely an oversight?
For example, in
elements/userlevel/fromdevice.cc
:while in
elements/userlevel/fromdpdkdevice.cc
, it's only:It would be good to have the mac_header set, since then one could
const click_ether *eth = p_in->mac_header();
independently of what kind of source the packet came through (FromDevice(), FromDPDKDevice(), PCAP...)I'm happy to submit a patch if the community says that it would be OK to set it.
Keep up the good work!
The text was updated successfully, but these errors were encountered: