From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752793AbbH0EMv (ORCPT ); Thu, 27 Aug 2015 00:12:51 -0400 Received: from mail.efficios.com ([78.47.125.74]:41398 "EHLO mail.efficios.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750884AbbH0EMt (ORCPT ); Thu, 27 Aug 2015 00:12:49 -0400 X-Greylist: delayed 479 seconds by postgrey-1.27 at vger.kernel.org; Thu, 27 Aug 2015 00:12:49 EDT Date: Thu, 27 Aug 2015 04:04:42 +0000 (UTC) From: Mathieu Desnoyers To: Andrew Morton Cc: LKML , linux-api Message-ID: <1721242013.30076.1440648282669.JavaMail.zimbra@efficios.com> Subject: Allocating sys_membarrier syscall number on other archs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [78.47.125.74] X-Mailer: Zimbra 8.6.0_GA_1178 (ZimbraWebClient - FF40 (Linux)/8.6.0_GA_1178) Thread-Topic: Allocating sys_membarrier syscall number on other archs Thread-Index: IJLS7tl/2Ny/qjJGIGty/9Xy0kEbHw== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Andrew, The sys_membarrier patches you have in your tree target x86 32-64 and generic, but I did not allocate the system call number on other architectures to minimize the amount of collisions, and because I do not have all those architectures handy. How would you recommend to proceed to allocate those ? sys_membarrier is pretty much architecture agnostic: it takes two integer parameters, and the only function it calls, synchronize_sched(), is available on all architectures. Thanks, Mathieu -- Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com