From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] perhaps a performance optimization
Date: Sun, 24 Apr 2016 23:45:45 +0300 [thread overview]
Message-ID: <249A79A8-D229-403B-A21E-72C57A012C6F@gmail.com> (raw)
In-Reply-To: <CAA93jw7uzfg-JFhCZegzKeKDFJkti4Rd79OkktAOR5FSkYotPQ@mail.gmail.com>
> On 24 Apr, 2016, at 18:44, Dave Taht <dave.taht@gmail.com> wrote:
>
> thought: since it takes two data packets for tcp to release an ack,
> perhaps it is better in some circumstances (notably with offloads
> enabled) to peel at quantum * 2,
> still delivering packets with a quantum (with a max of a mtu), so that
> delivering two unpeeled packets would cost that flow a DRR round, but
> save a lot on peeling overhead.
If a GSO packet is less than an MTU in total, surely it’ll peel into a single packet anyway? I don’t see where the gain is.
- Jonathan Morton
prev parent reply other threads:[~2016-04-24 20:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-24 15:44 Dave Taht
2016-04-24 20:45 ` Jonathan Morton [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=249A79A8-D229-403B-A21E-72C57A012C6F@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.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