Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 8 Feb 2002 07:32:52 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 8 Feb 2002 07:32:42 -0500 Received: from ns.caldera.de ([212.34.180.1]:35021 "EHLO ns.caldera.de") by vger.kernel.org with ESMTP id ; Fri, 8 Feb 2002 07:32:31 -0500 Date: Fri, 8 Feb 2002 13:31:07 +0100 Message-Id: <200202081231.g18CV7e31341@ns.caldera.de> From: Christoph Hellwig To: mingo@elte.hu (Ingo Molnar) Cc: Martin Wirth , linux-kernel , akpm , torvalds , rml , nigel To: yodaiken Subject: Re: [RFC] New locking primitive for 2.5 X-Newsgroups: caldera.lists.linux.kernel In-Reply-To: User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (Linux/2.4.13 (i686)) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org In article you wrote: > i think one example *could* be to turn inode->i_sem into a combi-lock. Eg. > generic_file_llseek() could use the spin variant. No. i_sem should be split into a spinlock for short-time accessed fields that get written to even if the file content is only read (i.e. atime) and a read-write semaphore. - 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/