RFC Revamp PPP fragmentation handling
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest4 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | ppp: Clean up kernel log messages.drivers/ | +50 | 0 replies | |
| 2/4 | ppp: Reconstruct fragmented packets using frag lists instead of copying.drivers/ | +21 | 0 replies | |
| 3/4 | net: Add safe reverse SKB queue walkers.include/ | +9 | 0 replies | |
| 4/4 | ppp: Use SKB queue abstraction interfaces in fragment processing.drivers/ | +16 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC PATCH 0/4] Revamp PPP fragmentation handling
If someone uses PPP fragmentation actively and can test this code out, I'd really appreciate it.
The main goal is to make the fragmentation code not reference the internals of our SKB queue and list implementation.
Along the way the printk's were also cleaned up, and also instead of copying fragments into newly allocated linear skbs, we use frag lists.