netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Cc: Alexander Duyck <alexander.duyck@gmail.com>,
	Netdev <netdev@vger.kernel.org>,
	Eric Dumazet <eric.dumazet@gmail.com>,
	"Alexander Duyck" <alexander.h.duyck@intel.com>
Subject: Re: [PATCH net-next v1] gso: Support partial splitting at the frag_list pointer
Date: Mon, 29 Aug 2016 14:02:31 +0200	[thread overview]
Message-ID: <20160829120231.GZ3735@gauss.secunet.com> (raw)
In-Reply-To: <20160825121718.GA13235@localhost.localdomain>

On Thu, Aug 25, 2016 at 09:17:18AM -0300, Marcelo Ricardo Leitner wrote:
> On Thu, Aug 25, 2016 at 09:31:26AM +0200, Steffen Klassert wrote:
> > 
> > Just to understand what you are doing. You generate MTU sized linear
> > buffers in sctp and then, skb_gro_receive() chains up these buffers
> > at the frag_list pointer. skb_gro_receive() does this because
> > skb_gro_offset is null and skb->head_frag is not set in your case.
> > 
> > At segmentation, you just need to split at the frag_list pointer
> > because you know that the chained buffers fit the MTU, right?
> > 
> 
> Correct. Just note that these buffers fit the MTU, but not necessary
> uses all of it. That is main point in here, variable segmentation size.

Thanks for the info. This is a very interesting concept, maybe I can use
it for IPsec too.

  reply	other threads:[~2016-08-29 12:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23  5:20 [PATCH net-next v1] gso: Support partial splitting at the frag_list pointer Steffen Klassert
2016-08-23 14:47 ` Alexander Duyck
2016-08-24  9:32   ` Steffen Klassert
2016-08-24 16:27     ` Alexander Duyck
2016-08-24 17:25       ` Marcelo Ricardo Leitner
2016-08-25  7:31         ` Steffen Klassert
2016-08-25 12:17           ` Marcelo Ricardo Leitner
2016-08-29 12:02             ` Steffen Klassert [this message]
2016-08-25 11:00       ` Steffen Klassert
2016-08-25 12:38         ` Marcelo Ricardo Leitner
2016-08-25 16:02         ` Alexander Duyck
2016-08-29 12:00           ` Steffen Klassert
2016-08-26 20:36         ` Shmulik Ladkani
2016-08-26 20:45           ` Alexander Duyck
2016-08-27  7:47             ` Shmulik Ladkani
2016-08-26 20:59         ` 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=20160829120231.GZ3735@gauss.secunet.com \
    --to=steffen.klassert@secunet.com \
    --cc=alexander.duyck@gmail.com \
    --cc=alexander.h.duyck@intel.com \
    --cc=eric.dumazet@gmail.com \
    --cc=marcelo.leitner@gmail.com \
    --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).