Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755666AbdGXRom (ORCPT ); Mon, 24 Jul 2017 13:44:42 -0400 Received: from mail-oi0-f65.google.com ([209.85.218.65]:35120 "EHLO mail-oi0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754175AbdGXRng (ORCPT ); Mon, 24 Jul 2017 13:43:36 -0400 MIME-Version: 1.0 In-Reply-To: <8760ek5ics.fsf_-_@xmission.com> References: <87o9shg7t7.fsf_-_@xmission.com> <20170718140651.15973-7-ebiederm@xmission.com> <878tjlbqpt.fsf@xmission.com> <8760ek5ics.fsf_-_@xmission.com> From: Linus Torvalds Date: Mon, 24 Jul 2017 10:43:34 -0700 X-Google-Sender-Auth: tuDsYqOptcEHz2GCKrpSDein5D8 Message-ID: Subject: Re: Simplfying copy_siginfo_to_user To: "Eric W. Biederman" Cc: Linux Kernel Mailing List , Andy Lutomirski , Al Viro , Oleg Nesterov , Andrei Vagin , Thomas Gleixner , Greg KH , Andrey Vagin , Serge Hallyn , Pavel Emelyanov , Cyrill Gorcunov , Peter Zijlstra , Willy Tarreau , "linux-arch@vger.kernel.org" , Linux API , Linux Containers , Michael Kerrisk Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 745 Lines: 18 On Sat, Jul 22, 2017 at 1:25 PM, Eric W. Biederman wrote: > I played with some clever changes such as limiting the copy to 48 bytes, > disabling the memset and the like but I could not get a strong enough > signal to say that any one change removed the extra or a clear part of > it 20ns. What CPU did you use? Because the SMAP bit in particular matters. The field-by-field copies are extremely slow on modern CPU's that implement SMAP, unless you also use the special "unsafe_put_user()" code (or the nasty old put_user_ex() code that some of the x86 signal code uses). So one of the advantages of just copy_to_user() ends up being visible only on Broadwell+ (or whatever the SMAP cutoff is). Linus