From: <erik.hugne@ericsson.com>
To: <netdev@vger.kernel.org>, <jon.maloy@ericsson.com>,
<maloy@donjonn.com>, <paul.gortmaker@windriver.com>
Cc: <ying.xue@windriver.com>, <tipc-discussion@lists.sourceforge.net>,
Erik Hugne <erik.hugne@ericsson.com>
Subject: [PATCH net-next v3 0/3] tipc: message reassembly using fragment chain
Date: Wed, 6 Nov 2013 09:28:04 +0100 [thread overview]
Message-ID: <1383726487-27929-1-git-send-email-erik.hugne@ericsson.com> (raw)
From: Erik Hugne <erik.hugne@ericsson.com>
We introduce a new reassembly algorithm that improves performance
and eliminates the risk of causing out-of-memory situations.
v3: -Use skb_try_coalesce, and revert to fraglist if this does not succeed.
-Make sure reassembly list head is uncloned.
v2: -Rebased on Ying's indentation fix.
-Node unlock call in msg_fragmenter case moved from patch #2 to #1.
('continue' with this lock held would cause spinlock recursion if only
patch #1 is used)
Erik Hugne (3):
tipc: don't reroute message fragments
tipc: message reassembly using fragment chain
tipc: reassembly failures should cause link reset
net/tipc/bcast.c | 16 ++++--
net/tipc/link.c | 164 ++++++++++++++++--------------------------------------
net/tipc/link.h | 20 +++++--
net/tipc/msg.h | 12 ----
net/tipc/node.c | 7 ++-
net/tipc/node.h | 6 +-
6 files changed, 80 insertions(+), 145 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-11-06 8:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 8:28 erik.hugne [this message]
2013-11-06 8:28 ` [PATCH net-next v3 1/3] tipc: don't reroute message fragments erik.hugne
2013-11-06 8:28 ` [PATCH net-next v3 2/3] tipc: message reassembly using fragment chain erik.hugne
2013-11-06 8:28 ` [PATCH net-next v3 3/3] tipc: reassembly failures should cause link reset erik.hugne
2013-11-07 23:31 ` [PATCH net-next v3 0/3] tipc: message reassembly using fragment chain David Miller
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=1383726487-27929-1-git-send-email-erik.hugne@ericsson.com \
--to=erik.hugne@ericsson.com \
--cc=jon.maloy@ericsson.com \
--cc=maloy@donjonn.com \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.com \
/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;
as well as URLs for NNTP newsgroup(s).