packet: Sock-diag extension for packet sockets (beginning)
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | packet: Introduce net/packet/internal.h headernet/ net/ | +105 | 0 replies | |
| 2/4 | packet: Diag core and basic socket info dumpinginclude/ include/ net/ +2 more | +139 | 0 replies | |
| 2/4 | packet: Report more packet sk info via diag moduleinclude/ net/ | +56 | 0 replies | |
| 4/4 | packet: Report socket mclist info via diag moduleinclude/ net/ | +49 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH net-next 0/4] packet: Sock-diag extension for packet sockets (beginning)
There's a set of stuff residing on a AF_PACKET socket which is currently write-only -- rings, copy_thresh and mclist. But we need to know these while doing the checkpoint-restore.
As a solution for the similar problem with unix sockets, the sock-diag engine was developed, so here's the basic implementation of the packet sockets extension. It doesn't report rings, fanout and stats, but it can be easily added later.
I'd like to mention, that it's not a strict requirement, that the diag is used for getting info about sockets, it would be perfectly fine just to fix the packet getsockopt callback to return the desired info. So, if the diag for packet sockets is for any reason unacceptable, just let me know.
Thanks,
Pavel