From: Nuutti Kotivuori <naked@iki.fi>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: per-session QoS
Date: Fri, 06 Feb 2004 03:43:07 +0000 [thread overview]
Message-ID: <87isikg9f8.fsf@iki.fi> (raw)
In-Reply-To: <874qu5ge19.fsf@iki.fi>
Ben wrote:
> 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.
Dropping packets will not mean losing data - it just means that the
TCP connections have to resend the packets and in general means that
the connection will throttle itself to the configured rate.
But ingress filtering as it is now works exactly like that. The packet
that you are receiving has already reached your machine and you either
drop it or accept it. If you wish to do something further, you can
look into IMQ.
> 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.
Right, well, it probably is the easiest solution - just note that you
will be working from behind your own receive buffers and tcp windows,
which means that the connection might initially accept (burst) more
data than you expect before the buffers fill.
-- Naked
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-02-06 3:43 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
2004-02-06 3:43 ` Nuutti Kotivuori [this message]
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=87isikg9f8.fsf@iki.fi \
--to=naked@iki.fi \
--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.