From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org
Subject: [RFC PATCH 0/4] Revamp PPP fragmentation handling
Date: Tue, 05 Oct 2010 19:52:14 -0700 (PDT) [thread overview]
Message-ID: <20101005.195214.226791121.davem@davemloft.net> (raw)
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.
reply other threads:[~2010-10-06 2:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101005.195214.226791121.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox