From: Jonathan Morton <chromatix99@gmail.com>
To: Felix Resch <fuller@beif.de>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] conntrack lookup continuation
Date: Tue, 31 Jan 2017 23:14:05 +0200 [thread overview]
Message-ID: <6BA19F35-E3BB-48C4-9010-2153908E1DFA@gmail.com> (raw)
In-Reply-To: <1010949359.501064.1485874182374@webmail.strato.de>
> On 31 Jan, 2017, at 16:49, Felix Resch <fuller@beif.de> wrote:
>
> Since we now already do the conntrack-lookup for the nat keyword, would it be
> expensive to implement a kind of internal conntrack-mark-and-restore by cake-tin?
>
> E.g. when traffic leaves throu canke tin#x, the conntrack entry will get a fwmark and return traffic is put in the corresponding tin/bin on the ingress cake.
That’s an interesting idea. At this point I don’t know how easy it is to implement, though.
Certainly we need to clean up some other things first.
- Jonathan Morton
next prev parent reply other threads:[~2017-01-31 21:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 14:49 Felix Resch
2017-01-31 21:14 ` Jonathan Morton [this message]
2017-02-03 16:42 ` John Sager
2017-02-03 17:08 ` Dave Taht
2017-02-03 19:01 ` John Sager
2017-02-03 19:30 ` Jonathan Morton
2017-02-03 21:25 ` John Sager
2017-02-04 5:51 ` Konstantin Shalygin
2017-02-04 9:12 ` John Sager
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=6BA19F35-E3BB-48C4-9010-2153908E1DFA@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=fuller@beif.de \
/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