From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: George Amanakis <gamanakis@gmail.com>
Cc: Jonathan Morton <chromatix99@gmail.com>,
Pete Heist <peteheist@gmail.com>,
Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] allocate_src allocate_dst
Date: Sat, 25 Nov 2017 20:49:45 +0000 [thread overview]
Message-ID: <2F2BFC0D-1C48-42C0-B7EE-82F4A237B7CC@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <07221ab0-2e71-aeff-17e7-54684f686a35@gmail.com>
Ooops, sorry, dodge merge on my part from my work tree back to cobalt. A fix & PR will be with you shortly…. apologies.
Kevin
> On 25 Nov 2017, at 20:03, George Amanakis <gamanakis@gmail.com> wrote:
>
> I think we missed an "allocate_host" in cake_hash(), line ~810:
>
> if (allocate_host) {
> srchost_idx = srchost_hash % CAKE_QUEUES;
> inner_hash = srchost_idx % CAKE_SET_WAYS;
> outer_hash = srchost_idx - inner_hash;
> for (i = 0, k = inner_hash; i < CAKE_SET_WAYS;
> i++, k = (k + 1) % CAKE_SET_WAYS) {
> if (q->hosts[outer_hash + k].srchost_tag ==
> srchost_hash)
> goto found_src;
> }
>
> On 11/25/2017 2:04 PM, Jonathan Morton wrote:
>> Gotos are fairly common in kernel code, chiefly for exception handling. Obviously structured code is still preferred where it makes sense, but there are cases where it would actually confuse matters.
>>
>> I hope to be able to spend most of tomorrow going over the code as it currently stands. I even have an up-to-date net-next tree on one of my machines to build against.
>>
>> - Jonathan Morton
>>
>>
>> _______________________________________________
>> Cake mailing list
>>
>> Cake@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cake
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
next prev parent reply other threads:[~2017-11-25 20:49 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 [this message]
2017-11-25 21:20 ` Kevin Darbyshire-Bryant
2017-11-26 10:19 ` Kevin Darbyshire-Bryant
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=2F2BFC0D-1C48-42C0-B7EE-82F4A237B7CC@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=gamanakis@gmail.com \
--cc=peteheist@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