From: Nikolai Lusan <nikolai@lusan.id.au>
To: netfilter@vger.kernel.org
Subject: QoS in Netfilter
Date: Wed, 16 Apr 2014 18:57:43 +1000 [thread overview]
Message-ID: <1397638663.12394.1.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 140 bytes --]
Hi,
So the merits of MARK vs. CLASSIFY? What do people think is the best way
of using QoS?
--
Nikolai Lusan <nikolai@lusan.id.au>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2014-04-16 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 8:57 Nikolai Lusan [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-18 1:08 QoS in Netfilter Neal Murphy
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1397638663.12394.1.camel@localhost \
--to=nikolai@lusan.id.au \
--cc=netfilter@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).