From: marcelo.leitner@gmail.com
To: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Cc: netdev@vger.kernel.org, rds-devel@oss.oracle.com,
santosh.shilimkar@oracle.com, davem@davemloft.net,
eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 0/2] pskb_extract() helper function.
Date: Fri, 22 Apr 2016 20:23:01 -0300 [thread overview]
Message-ID: <20160422232301.GA1594@localhost.localdomain> (raw)
In-Reply-To: <cover.1461086306.git.sowmini.varadhan@oracle.com>
On Wed, Apr 20, 2016 at 03:17:40AM -0700, Sowmini Varadhan wrote:
> This patchset follows up on the discussion in
> https://www.mail-archive.com/netdev@vger.kernel.org/msg105090.html
>
> For RDS-TCP, we have to deal with the full gamut of
> nonlinear sk_buffs, including all the frag_list variants.
> Also, the parent skb has to remain unchanged, while the clone
> is queued for Rx on the PF_RDS socket.
>
> Patch 1 of this patchset adds a pskb_extract() function that
> does all this without the redundant memcpy's in pskb_expand_head()
> and __pskb_pull_tail().
I applied this patchset and updated SCTP to also use it for data chunks.
My tests results were very similar to what I had without it. Varying to
better or worse, tending worse. Thing is, SCTP always works on
linearized skbs as it can't crawl on fragments, so those clone/trim
operations are just offset adjusts regarding the data, and it's shared.
With pskb_extract, it implies in a new memory allocation and a copy,
even in this best case, so for SCTP, for now, it's actually a drawback
I'm afraid.
Marcelo
next prev parent reply other threads:[~2016-04-22 23:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 10:17 [PATCH net-next 0/2] pskb_extract() helper function Sowmini Varadhan
2016-04-20 10:17 ` [PATCH net-next 1/2] skbuff: Add " Sowmini Varadhan
2016-04-22 23:27 ` marcelo.leitner
2016-04-20 10:17 ` [PATCH net-next 2/2] RDS: TCP: Call " Sowmini Varadhan
2016-04-22 23:23 ` marcelo.leitner [this message]
2016-04-22 23:41 ` [PATCH net-next 0/2] " Sowmini Varadhan
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=20160422232301.GA1594@localhost.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=santosh.shilimkar@oracle.com \
--cc=sowmini.varadhan@oracle.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).