Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 27 Jul 2001 14:01:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 27 Jul 2001 14:01:40 -0400 Received: from e22.nc.us.ibm.com ([32.97.136.228]:8660 "EHLO e22.nc.us.ibm.com") by vger.kernel.org with ESMTP id ; Fri, 27 Jul 2001 14:01:29 -0400 Date: Fri, 27 Jul 2001 11:01:00 -0700 (PDT) From: Sridhar Samudrala To: Alan Cox cc: Sridhar Samudrala , linux-kernel@vger.kernel.org, linux-net@vger.kernel.org, lartc@mailman.ds9a.nl, diffserv-general@lists.sourceforge.net, kuznet@ms2.inr.ac.ru, rusty@rustcorp.com.au Subject: Re: [PATCH] Inbound Connection Control mechanism: Prioritized Accept In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Original-Recipient: rfc822;linux-kernel-outgoing 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. Thanks Sridhar 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. > > http://oss.software.ibm.com/qos > > > > 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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/