From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 11 Jun 2001 23:03:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 11 Jun 2001 23:03:09 -0400 Received: from horus.its.uow.edu.au ([130.130.68.25]:8447 "EHLO horus.its.uow.edu.au") by vger.kernel.org with ESMTP id ; Mon, 11 Jun 2001 23:03:03 -0400 Message-ID: <3B258479.472F5C91@uow.edu.au> Date: Tue, 12 Jun 2001 12:54:49 +1000 From: Andrew Morton X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.3-ac13 i686) X-Accept-Language: en MIME-Version: 1.0 To: Linus Torvalds CC: Andrea Arcangeli , Ingo Molnar , Kernel Mailing List Subject: Re: softirq bugs in pre2 In-Reply-To: <20010611193703.S5468@athlon.random> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Linus Torvalds wrote: > > On Mon, 11 Jun 2001, Andrea Arcangeli wrote: > > > > Since I mentioned the copy-user latency fixes (even if offtopic with the > > above) this is the URL for trivial merging: > > The copy-user latency fixes only make sense for out-of-line copies. If > we're going to have a conditional function call to "schedule()", we do not > want to inline the dang thing any more - we've just destroyed our register > set etc anyway. It's overkill. This adds many hundreds of scheduling points to the kernel, of which we need only five. It makes more sense to simply open-code those five. - generic_file_read/write - read /dev/zero, /dev/mem - memcpy_to_iovec() This will by no means provide a low-latency kernel, but it will fix the most common causes of poor interactivity in normal use. Just doing generic_file_read/write would suffice, actually.