From: jamal <hadi@cyberus.ca>
To: <diffserv-general@lists.sourceforge.net>
Cc: <kuznet@ms2.inr.ac.ru>, <alan@lxorguk.ukuu.org.uk>,
<linux-kernel@vger.kernel.org>, <linux-net@vger.kernel.org>,
<lartc@mailman.ds9a.nl>, <rusty@rustcorp.com.au>,
<thiemo@sics.se>, Sridhar Samudrala <samudrala@us.ibm.com>,
Renu Tewari <tewarir@us.ibm.com>
Subject: Re: [Linux Diffserv] Re: [PATCH] Inbound Connection Control mechanism: Prioritized Accept Queue
Date: Mon, 30 Jul 2001 15:26:46 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.30.0107301515090.7013-100000@shell.cyberus.ca> (raw)
In-Reply-To: <OF8753E938.DCEA2C85-ON85256A99.005DE1F6@pok.ibm.com>
For startes, can you fix
oss.software.ibm.com so it respects ECN?
In regards to policing SYNs i am not sure what additional
value you provide to the mechanisms currently available under
2.4 ingress traffic policing; the simplest example we provided
was on SYN policing albeit for DoS prevention.
Since i refuse to turn off ECN, i cant access your web page
You can use the skbmark to prioritize based on policies
installed on the ingress and drop early ...
Incase you are using this scheme already you should stick to the
ingress policer which uses a dual Token Bucket not what netfilter uses..
cheers,
jamal
On Mon, 30 Jul 2001, Douglas M Freimuth wrote:
>
>
> On Fri, 27 Jul 2001,Sridhar wrote:
>
> >The documentation on HOWTO use this patch and the test results which show
> an
> >improvement in connection rate for higher priority classes can be found at
> our
> >project website.
> > http://oss.software.ibm.com/qos
>
> For additional detail regarding the Prioritized Accept Queue (PAQ)
> patch please read
> "Kernel Mechanisms for Service Differentiation in Overloaded Web Servers"
> originally published in
> the 2001 Proceedings of the USENIX Annual Technical Conference
> (USENIX Association, 2001), pp. 189-202. at the following USENIX site:
>
> http://www.usenix.org/publications/library/proceedings/usenix01/voigt.html
>
> For USENIX nonmembers later this week will "reprint" this USENIX paper on
> our project
> website.
> http://oss.software.ibm.com/qos
>
> --Doug
> =================================================================
> Doug Freimuth
> IBM TJ Watson Research Center
> Office 914-784-6221
> dmfreim@us.ibm.com
>
>
> _______________________________________________
> Diffserv-general mailing list
> Diffserv-general@lists.sourceforge.net
> http://lists.sourceforge.net/lists/listinfo/diffserv-general
>
next prev parent reply other threads:[~2001-07-30 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 17:36 Douglas M Freimuth
2001-07-30 19:26 ` jamal [this message]
2001-07-30 22:08 ` Sridhar Samudrala
2001-07-29 21:27 ` [Linux Diffserv] Re: [PATCH] Inbound Connection Control mechanism: Alan Cox
2001-08-03 16:40 ` Sridhar Samudrala
2001-08-03 18:33 ` kuznet
2001-07-30 22:28 ` [Linux Diffserv] Re: [PATCH] Inbound Connection Control mechanism: Prioritized Accept Queue Justin Guyett
2001-07-31 10:24 ` Chris Wedgwood
2001-07-31 6:13 ` David S. Miller
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=Pine.GSO.4.30.0107301515090.7013-100000@shell.cyberus.ca \
--to=hadi@cyberus.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=diffserv-general@lists.sourceforge.net \
--cc=kuznet@ms2.inr.ac.ru \
--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 \
--cc=tewarir@us.ibm.com \
--cc=thiemo@sics.se \
/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®