mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kuznet@ms2.inr.ac.ru
To: samudrala@us.ibm.com (Sridhar Samudrala)
Cc: alan@lxorguk.ukuu.org.uk, samudrala@us.ibm.com,
	linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
	lartc@mailman.ds9a.nl, diffserv-general@lists.sourceforge.net,
	rusty@rustcorp.com.au
Subject: Re: [PATCH] Inbound Connection Control mechanism: Prioritized Accept
Date: Sat, 28 Jul 2001 23:12:05 +0400 (MSK DST)	[thread overview]
Message-ID: <200107281912.XAA17362@ms2.inr.ac.ru> (raw)
In-Reply-To: <Pine.LNX.4.21.0107271140330.14328-100000@w-sridhar2.des.sequent.com> from "Sridhar Samudrala" at Jul 27, 1 12:55:25 pm

Hello!

> Low priority connections can clog the accept queue only when there are no
> high priority connection requests coming along. As soon as a slot becomes empty
> in the accept queue, it becomes available for a high priority connection.

And in presence of persistent low priority traffic, high priority connection
will not have any chances to take this slot. When high priority connection
arrives all the slots are permanently busy with low ones.

> If that happens, TCP SYN policing can be employed to limit the rate of low 
> priority connections getting into accept queue. 

After this your patch is not required at all. :-)

All the effect is a bit better latency, not a big win.


> dropped simply because there is no room for that class although there is room 
> for higher priority classes and there are no incoming higher priority 
> connections. 

ABC of resource control. If you have finite resource and want to give
better service to class A, you must reserve for it some bits of resource
or must be able to preempt other classes.

Alexey

  reply	other threads:[~2001-07-28 19:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-27 17:10 [PATCH] Inbound Connection Control mechanism: Prioritized Accept Queue Sridhar Samudrala
2001-07-27 17:25 ` [PATCH] Inbound Connection Control mechanism: Prioritized Accept Alan Cox
2001-07-27 18:01   ` Sridhar Samudrala
2001-07-27 18:07     ` Alan Cox
2001-07-27 18:04   ` kuznet
2001-07-27 19:55     ` Sridhar Samudrala
2001-07-28 19:12       ` kuznet [this message]
2001-07-28 20:01         ` Thiemo Voigt
2001-07-29 16:25           ` kuznet
2001-07-30  7:40             ` Sridhar Samudrala
2001-08-01 23:22               ` Alexey Kuznetsov
2001-08-02 17:17                 ` Sridhar Samudrala
2001-08-02 22:31                   ` Alexey Kuznetsov

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=200107281912.XAA17362@ms2.inr.ac.ru \
    --to=kuznet@ms2.inr.ac.ru \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=diffserv-general@lists.sourceforge.net \
    --cc=lartc@mailman.ds9a.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=samudrala@us.ibm.com \
    /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

all inboxes | Powered by JetHome®