Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753473AbaJTXlq (ORCPT ); Mon, 20 Oct 2014 19:41:46 -0400 Received: from mail-yh0-f41.google.com ([209.85.213.41]:43479 "EHLO mail-yh0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751192AbaJTXlp (ORCPT ); Mon, 20 Oct 2014 19:41:45 -0400 MIME-Version: 1.0 In-Reply-To: <20141020222841.419869904@infradead.org> References: <20141020215633.717315139@infradead.org> <20141020222841.419869904@infradead.org> Date: Mon, 20 Oct 2014 16:41:45 -0700 X-Google-Sender-Auth: TzNBWL-Yfb8nBI9TNHum136YmFk Message-ID: Subject: Re: [RFC][PATCH 4/6] SRCU free VMAs From: Linus Torvalds To: Peter Zijlstra Cc: Paul McKenney , Thomas Gleixner , Andrew Morton , Rik van Riel , Mel Gorman , Oleg Nesterov , Ingo Molnar , Minchan Kim , KAMEZAWA Hiroyuki , Al Viro , Lai Jiangshan , Davidlohr Bueso , Linux Kernel Mailing List , linux-mm Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 20, 2014 at 2:56 PM, Peter Zijlstra wrote: > Manage the VMAs with SRCU such that we can do a lockless VMA lookup. Can you explain why srcu, and not plain regular rcu? Especially as you then *note* some of the problems srcu can have. Making it regular rcu would also seem to make it possible to make the seqlock be just a seqcount, no? Linus -- 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/