From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] allocate_src allocate_dst
Date: Sun, 26 Nov 2017 10:19:48 +0000 [thread overview]
Message-ID: <8147C2DB-D89A-4567-80AA-F126D2CDEDBC@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <C9D06AAA-DF43-46D5-860E-3550B3C5C0A5@darbyshire-bryant.me.uk>
Have to say, my perception is that I’ve a small cpu usage improvement for my use case with these changes. Then I would expect that ‘cos I use ‘dual-srchost’ on egress and ‘dual-dsthost’ on ingress, so I’m saving running the dst/src host allocation code on egress/ingress respectively.
Of course for the standard ‘triple-isolate’ things will be slightly slower ‘cos of the conditional flag setting.
Cheers,
Kevin
prev parent reply other threads:[~2017-11-26 10:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-25 3:59 Dave Taht
2017-11-25 14:08 ` Kevin Darbyshire-Bryant
2017-11-25 15:19 ` Jonathan Morton
2017-11-25 16:36 ` Kevin Darbyshire-Bryant
2017-11-25 16:41 ` Jonathan Morton
2017-11-25 16:43 ` Kevin Darbyshire-Bryant
2017-11-25 16:46 ` Dave Taht
2017-11-25 17:07 ` Kevin Darbyshire-Bryant
2017-11-25 16:45 ` Dave Taht
2017-11-25 16:52 ` Dave Taht
2017-11-25 16:58 ` Dave Taht
2017-11-25 16:28 ` Pete Heist
[not found] ` <CAJq5cE1haW1AqfECJws1DF=AUGxoRar-5ODSPxv=pLRyGTABWg@mail.gmail.com>
[not found] ` <CAJq5cE1Rvz_Oa94kbfouoniZYtcK4qB5gtL1JngsZ_XdTnpQxw@mail.gmail.com>
2017-11-25 16:32 ` Jonathan Morton
2017-11-25 16:48 ` Dave Taht
2017-11-25 18:48 ` Pete Heist
[not found] ` <CAJq5cE15hirznu_Zhbr_om-+_s9T7YF+OKag4MQPW7iz7Bzn_Q@mail.gmail.com>
2017-11-25 19:04 ` Jonathan Morton
2017-11-25 20:03 ` George Amanakis
2017-11-25 20:49 ` Kevin Darbyshire-Bryant
2017-11-25 21:20 ` Kevin Darbyshire-Bryant
2017-11-26 10:19 ` Kevin Darbyshire-Bryant [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=8147C2DB-D89A-4567-80AA-F126D2CDEDBC@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=cake@lists.bufferbloat.net \
/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