From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f72.google.com (mail-pa0-f72.google.com [209.85.220.72]) by kanga.kvack.org (Postfix) with ESMTP id E31E46B0038 for ; Mon, 17 Oct 2016 05:32:57 -0400 (EDT) Received: by mail-pa0-f72.google.com with SMTP id os4so194772852pac.5 for ; Mon, 17 Oct 2016 02:32:57 -0700 (PDT) Received: from bombadil.infradead.org (bombadil.infradead.org. [2001:1868:205::9]) by mx.google.com with ESMTPS id z68si26656323pgz.5.2016.10.17.02.32.57 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 17 Oct 2016 02:32:57 -0700 (PDT) Date: Mon, 17 Oct 2016 02:32:55 -0700 From: Christoph Hellwig Subject: Re: [PATCH v3] mm: vmalloc: Replace purge_lock spinlock with atomic refcount Message-ID: <20161017093255.GA17523@infradead.org> References: <20161016061057.GA26990@infradead.org> <1476655575-6588-1-git-send-email-joelaf@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: To: Joel Fernandes Cc: Christoph Hellwig , LKML , "open list:MEMORY MANAGEMENT" , linux-rt-users@vger.kernel.org, Chris Wilson , Jisheng Zhang , John Dias , Andrew Morton On Sun, Oct 16, 2016 at 03:48:42PM -0700, Joel Fernandes wrote: > Also, one more thing about the barrier dances you mentioned, this will > also be done by the spinlock which was there before my patch. So in > favor of my patch, it doesn't make things any worse than they were and > actually fixes the reported issue while preserving the original code > behavior. So I think it is a good thing to fix the issue considering > so many people are reporting it and any clean ups of the vmalloc code > itself can follow. I'm not worried about having barriers, we use them all over our synchronization primitives. I'm worried about opencoding them instead of having them in these well defined helpers. So based on this discussion and the feedback from Nick I'll propose a new patch (or rather a series to make it more understandable) that adds a mutex, adds the lockbreak and gives sensible calling conventions to __purge_vmap_area_lazy. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org