Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: cam enih <nanericwang@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] CAKE on the bonding interface (master) or the bonded interfaces (slaves)?
Date: Thu, 16 Jan 2025 02:57:46 -0000	[thread overview]
Message-ID: <CAPB3MF4ApjawJtr=spCr92rBvPBwBnwGmwR+fsGdPot0pM6_zQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 286 bytes --]

Hi CAKE folks,

I'm new to traffic shaping, just a quick question here:

I have this virtual NIC set up and a few physical NICs bonded to it. Shall
I apply the CAKE algorithm on the virtual one or the physical ones, or all
of them? If either can do it, which is the best?

Thanks,
Eric

[-- Attachment #2: Type: text/html, Size: 396 bytes --]

             reply	other threads:[~2025-01-16  2:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16  2:57 cam enih [this message]
2025-06-06 13:45 ` [Cake] CAKE on the bonding interface (master) or the bondedinterfaces (slaves)? Nils Andreas Svee

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='CAPB3MF4ApjawJtr=spCr92rBvPBwBnwGmwR+fsGdPot0pM6_zQ@mail.gmail.com' \
    --to=nanericwang@gmail.com \
    --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