All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben <bench@silentmedia.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: per-session QoS
Date: Fri, 06 Feb 2004 03:27:51 +0000	[thread overview]
Message-ID: <1076038070.21071.12.camel@purple> (raw)
In-Reply-To: <874qu5ge19.fsf@iki.fi>

On Thu, 2004-02-05 at 18:03, Nuutti Kotivuori wrote:

> What you would wish to do is have a simple per connection token
> bucket, and just DROP every packet exceeding the rate in the
> connection, am I right?

I don't want to loose data, so dropping packets definately seems like
the wrong thing to do. Unless that's how ingress filters work? I haven't
used them before.

Fortunately I have access to the code of my server application, because
it sounds like the easiest thing is going to be to just put per-session
rate limiting into that.

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2004-02-06  3:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-06  2:03 [LARTC] Re: per-session QoS Nuutti Kotivuori
2004-02-06  3:27 ` Ben [this message]
2004-02-06  3:43 ` Nuutti Kotivuori

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=1076038070.21071.12.camel@purple \
    --to=bench@silentmedia.com \
    --cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.