Virtual ethernet device (v3)
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 14 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | Introduce the generic rtnl_create_link()include/ net/ | +57 | 0 replies | |
| 1/2 | Intruduce iplink_parse() routineinclude/ ip/ | +76 | 0 replies | |
| 2/2 | Virtual ethernet device driverdrivers/ drivers/ drivers/ +1 more | +445 | 14 replies | |
| 2/2 | Module for ip utility to support veth deviceip/ ip/ ip/ | +77 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] Virtual ethernet device (v3)
Veth stands for Virtual ETHernet. It is a simple tunnel driver that works at the link layer and looks like a pair of ethernet devices interconnected with each other.
Mainly it allows to communicate between network namespaces but it can be used as is as well.
Eric recently sent a similar driver called etun with the sysfs interface. This implementation uses another interface - the RTM_NRELINK message introduced by Patric.
The newlink callback is organized that way to make it easy to create the peer device in the separate namespace when we have them in kernel.
Changes from v.2.1:
* Made the generic routine for link creation to be used by veth driver, any other tunnel driver that needs to create several devices at once and rtnl_newlink() code.
Changes from v.2:
* Rebase over latest netdev tree. No actual changes;
* Small code rework.
Changes from v.1:
* percpu statistics;
* standard convention for nla policy names;
* module alias added;
* xmit function fixes noticed by Patric;
* code cleanup.
The patch for an ip utility is also provided.