Re: [PATCH] Inbound Connection Control mechanism: Prioritized Accept

From: Sridhar Samudrala (
Date: Fri Jul 27 2001 - 13:01:00 EST

There are couple of reasons why prioritization in kernel works better than at
user level.
* The kernel mechanisms are more efficient and scalable than the user space
  mechanism. Non compliant connection requests are discarded earlier reducing the
  queuing time of the compliant requests, in particular less CPU is consumed and
  the context switch to userspace is avoided.
* Doing it in user space requires changes to existing applications which is not
  always possible.


On Fri, 27 Jul 2001, Alan Cox 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.
> >
> >
> > We would appreciate any comments or suggestions.
> Simple question.
> How is this different from having a single userspace thread in your
> application which accepts connections as they come in and then hands them
> out in an order it chooses, if need be erorring and closing some ?
> Alan

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

This archive was generated by hypermail 2b29 : Tue Jul 31 2001 - 21:00:34 EST