From: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
To: samudrala@us.ibm.com (Sridhar Samudrala)
Cc: kuznet@ms2.inr.ac.ru, thiemo@sics.se, dmfreim@us.ibm.com,
hadi@cybeus.ca, linux-kernel@vger.kernel.org,
linux-net@vger.kernel.org,
diffserv-general@lists.sourceforge.net, rusty@rustcorp.com.au
Subject: Re: [PATCH] Inbound Connection Control mechanism: Prioritized Accept
Date: Fri, 3 Aug 2001 02:31:51 +0400 (MSD) [thread overview]
Message-ID: <200108022231.CAA00375@mops.inr.ac.ru> (raw)
In-Reply-To: <Pine.LNX.4.21.0108020956320.25553-100000@w-sridhar2.des.sequent.com> from "Sridhar Samudrala" at Aug 2, 1 10:17:11 am
Hello!
> This looks like an elegant way of prioritizing without penalizing low priority
> connections in the absence of high priority ones.
> There may be an issue with sockets in accept queue which have received data.
> Is it OK to move a socket which has already received some data back to SYN-RECV
> state and expect the data to be resent?
No, if you ACKed it. 500msec is maximum... Not so big number.
But inside 500msec there are no problems with HTTP, where this ACK is
better to maximally delay to piggyback to reply in any case.
Alexey
prev parent reply other threads:[~2001-08-03 17:23 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
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 [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=200108022231.CAA00375@mops.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=diffserv-general@lists.sourceforge.net \
--cc=dmfreim@us.ibm.com \
--cc=hadi@cybeus.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=samudrala@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®