dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Olivier MATZ <olivier.matz-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Helmut Sim <simhelmut-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Alex Markuze <alex-I7wstvAgZDk@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: two tso related questions
Date: Wed, 17 Dec 2014 14:02:03 +0100	[thread overview]
Message-ID: <54917ECB.3080404@6wind.com> (raw)
In-Reply-To: <CAF8yGaGSZgGrO19AKFxsP+Oq6rLmoYvmVBmsyes+QfXT2E6vJw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi Helmut,

On 12/17/2014 08:17 AM, Helmut Sim wrote:
>>>>> While working on TSO based solution I faced the following two questions:
>>>>>
>>>>> 1.
>>>>> is there a maximum pkt_len to be used with TSO?, e.g. let's say if
>>>>> seg_sz
>>>>> is 1400 can the entire segmented pkt be 256K (higer than 64K) ?, then
>>>>> the
>>>>> driver gets a list of chanined mbufs while the first mbuf is set to TSO
>>>>> offload.

I think the limitations depend on:

- the window size advertised by the peer: your stack should handle this
   and not generate more packets that what the peer can receive

- the driver: on ixgbe, the maximum payload length is 2^18. I don't know
   if there is a limitation on number of chained descriptors.

I think we should define a way to know this limitation in the API. Maybe
a comment saying that the TSO length should not be higher than 256KB (or
fix it to 64KB in case future drivers do not support 256KB) is enough.

Regards,
Olivier

  parent reply	other threads:[~2014-12-17 13:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15 20:20 two tso related questions Helmut Sim
     [not found] ` <CAF8yGaERQQ6DGPOotsJcXWuEzF=otRyA_ei7nffy8-bfZGWdNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-16  9:10   ` Alex Markuze
     [not found]     ` <CAKfHP0WY8n1tyxw7jbeBU2EgrAziyv+1h+xAuLyQ7Uu9AgiSzw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-16 12:24       ` Helmut Sim
     [not found]         ` <CAF8yGaFO+VXnvh1Er=oWUPrbGqc46fJdCp7Wez3gNgcjLCdqZw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-16 14:04           ` Alex Markuze
     [not found]             ` <CAKfHP0XNNqOSGsZ4zVn3va5f+fxRsZCP=YVdXpUx=eYTVO8xhw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-17  7:17               ` Helmut Sim
     [not found]                 ` <CAF8yGaGSZgGrO19AKFxsP+Oq6rLmoYvmVBmsyes+QfXT2E6vJw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-17 13:02                   ` Olivier MATZ [this message]
     [not found]                     ` <54917ECB.3080404-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2015-01-04  8:50                       ` Helmut Sim
     [not found]                         ` <CAF8yGaEBVYRzWWDmmfxP7mG-o+oz8_ciDm+pSUoAWpBycjCObw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-04  9:57                           ` Alex Markuze
     [not found]                             ` <CAKfHP0W3jLTQeTvyKtUgKd0sVVDo1SA5coY=YgvqQpr6BDfNEA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-04 10:13                               ` Helmut Sim
     [not found]                                 ` <CAF8yGaHydSrgF7aWcXGy=AbmmpMKVmrjuqDtazFoeh6TRW+y0w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-05  8:53                                   ` Olivier MATZ

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=54917ECB.3080404@6wind.com \
    --to=olivier.matz-pdr9zngts4eavxtiumwx3w@public.gmane.org \
    --cc=alex-I7wstvAgZDk@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=simhelmut-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).