From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rusty Russell Subject: Re: [PATCH 0/3] sys_membarrier (x86, generic) Date: Tue, 06 Oct 2015 09:51:39 +1030 Message-ID: <87vbaknbp8.fsf@rustcorp.com.au> References: <1436561912-24365-1-git-send-email-mathieu.desnoyers@efficios.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: <1436561912-24365-1-git-send-email-mathieu.desnoyers-vg+e7yoeK/dWk0Htik3J/w@public.gmane.org> Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Andrew Morton Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Mathieu Desnoyers List-Id: linux-api@vger.kernel.org Mathieu Desnoyers writes: > Hi Andrew, > > Here is a repost of sys_membarrier, rebased on top of Linus commit > c4b5fd3fb2058b650447372472ad24e2a989f9f6 without any change since the > last v19 post other that proceeding to further testing. When merging > with other system calls, system call number conflicts should be quite > straightforward to handle, there is nothing special there. Hi Mathieu, Great to see this go in! One small note: it talks about threads, but membarrier as currently implemented would cover any shared memory. If you plan to optimize in future, that might not be the case: we'd want an address argument for those cases? Cheers, Rusty. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752199AbbJFCAG (ORCPT ); Mon, 5 Oct 2015 22:00:06 -0400 Received: from ozlabs.org ([103.22.144.67]:59069 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751330AbbJFCAC (ORCPT ); Mon, 5 Oct 2015 22:00:02 -0400 From: Rusty Russell To: Mathieu Desnoyers , Andrew Morton Cc: linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, Mathieu Desnoyers Subject: Re: [PATCH 0/3] sys_membarrier (x86, generic) In-Reply-To: <1436561912-24365-1-git-send-email-mathieu.desnoyers@efficios.com> References: <1436561912-24365-1-git-send-email-mathieu.desnoyers@efficios.com> User-Agent: Notmuch/0.17 (http://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Tue, 06 Oct 2015 09:51:39 +1030 Message-ID: <87vbaknbp8.fsf@rustcorp.com.au> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Mathieu Desnoyers writes: > Hi Andrew, > > Here is a repost of sys_membarrier, rebased on top of Linus commit > c4b5fd3fb2058b650447372472ad24e2a989f9f6 without any change since the > last v19 post other that proceeding to further testing. When merging > with other system calls, system call number conflicts should be quite > straightforward to handle, there is nothing special there. Hi Mathieu, Great to see this go in! One small note: it talks about threads, but membarrier as currently implemented would cover any shared memory. If you plan to optimize in future, that might not be the case: we'd want an address argument for those cases? Cheers, Rusty.