Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Felix Resch <fuller@beif.de>
To: cake@lists.bufferbloat.net
Subject: [Cake] conntrack lookup continuation
Date: Tue, 31 Jan 2017 15:49:42 +0100 (CET)	[thread overview]
Message-ID: <1010949359.501064.1485874182374@webmail.strato.de> (raw)

Hoi! 

(longtime lurker here)

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.

cheers
felix

             reply	other threads:[~2017-01-31 14:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31 14:49 Felix Resch [this message]
2017-01-31 21:14 ` Jonathan Morton
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=1010949359.501064.1485874182374@webmail.strato.de \
    --to=fuller@beif.de \
    --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