From: Alexander Duyck <alexander.h.duyck@intel.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net
Subject: [PATCH 0/2] Cleanups for head_frag usage and tcp_try_coalese
Date: Wed, 02 May 2012 20:38:50 -0700 [thread overview]
Message-ID: <20120503033018.5482.89902.stgit@gitlad.jf.intel.com> (raw)
I wrote up these patches earlier today to address issues related to the
splitting of reference counting into two seperate counts in the case of
skbs containing a head frag. In addition I have a secondary patch for
tcp_try_coalesce which is meant to be a general cleanup as I found it
difficult to read through the code as it was.
I have done some performance testing on the series with netperf and saw no
appreciable difference after these changes for the non-cloned case.
---
Alexander Duyck (2):
tcp: cleanup tcp_try_coalesce
net: Stop decapitating clones that have a head_frag
net/core/skbuff.c | 2 +
net/ipv4/tcp_input.c | 85 +++++++++++++++++++++++++-------------------------
2 files changed, 44 insertions(+), 43 deletions(-)
--
next reply other threads:[~2012-05-03 3:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 3:38 Alexander Duyck [this message]
2012-05-03 3:38 ` [PATCH 1/2] net: Stop decapitating clones that have a head_frag Alexander Duyck
2012-05-03 3:56 ` Eric Dumazet
2012-05-03 3:39 ` [PATCH 2/2] tcp: cleanup tcp_try_coalesce Alexander Duyck
2012-05-03 4:06 ` Eric Dumazet
2012-05-03 4:58 ` Alexander Duyck
2012-05-03 5:19 ` Eric Dumazet
2012-05-03 5:25 ` David Miller
[not found] ` <20120503.012502.44731688706812861.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2012-05-03 15:14 ` John W. Linville
2012-05-03 15:24 ` Guy, Wey-Yi
2012-05-03 17:07 ` John W. Linville
[not found] ` <20120503170727.GM9285-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2012-05-03 20:21 ` Guy, Wey-Yi
2012-05-03 5:41 ` Alexander Duyck
2012-05-03 5:50 ` David Miller
2012-05-03 7:08 ` Alexander Duyck
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=20120503033018.5482.89902.stgit@gitlad.jf.intel.com \
--to=alexander.h.duyck@intel.com \
--cc=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;
as well as URLs for NNTP newsgroup(s).