Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp725259imm; Thu, 13 Sep 2018 06:53:07 -0700 (PDT) X-Google-Smtp-Source: ANB0VdaxBYFFb4/mjepPFbraX139aEJfDv3rSLKRw67VnFY49EMXwHiCnN+Y+poD2BxuQRZdRiJs X-Received: by 2002:a17:902:68:: with SMTP id 95-v6mr7385949pla.248.1536846787770; Thu, 13 Sep 2018 06:53:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536846787; cv=none; d=google.com; s=arc-20160816; b=X2vpzMvXWyqM+83F2cgWwIFIoK7fCY7k8UqFq+g3rG3YH6vs77mMtveHYuly3JSFrF 5gxMQ1ERp82LZkE2LvOYWHzX25gg6KwrLArXUdP6IUFyhRQPY/9oTJeDz2qX2GVGW/Sw krym0uVwipo74YNmrYb3Bx0KBK/HGl6ysJk/BS5itiiCAYKNuQrYJ44kY0gDXjbp7X1J rFDJ1vu/OvODJAksUultb2ZDWMbMfnmFKfjErq1qzRpxyu7qwxqj8hG/PXHdqh/sW9UR DRuIpURWIitK7Z67MkGs7H/zXJM4ALyO9Pf5OM+8PAohQRcJShpjnbumG61OsWatvjSJ h/0g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=6Zuv0lBVysM4Yqcjnf8izA4zdYg8F7VNRQ7U2y0uZvI=; b=dxB+rpA3Owe7/xIcvTMK//vulY5UZMKyGRHptHJ9r0R8kp259IYMJYnjHIaeGMs+fK Lcx+9xxGj8lihKWBy9D/W77OgdFBaRfaozle08yWgeXfg+W7DRs49djlrHtOm7zrDGnr B1TjbmMyphWG7YC3Samgvxgu6PaT4emXnhl49S5hQgdiUGSFN2RsKTXoxKO+KjWO1I1B Tz0NnYkUtAr8vFMGyumjWt7C5goMDGFB7JKsaPScFu94/pRBqwtRfodhGvixr4rK10vY PmJkSX5yVIKcbS1v6I+VZOGjadUrV8xTi8PbkEiXtT+HyWMOX7xNrSx1B792n5djxN9j 8V6A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@zx2c4.com header.s=mail header.b=xAgadjPE; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=zx2c4.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y1-v6si3992746pgo.644.2018.09.13.06.52.52; Thu, 13 Sep 2018 06:53:07 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@zx2c4.com header.s=mail header.b=xAgadjPE; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=zx2c4.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731008AbeIMTCM (ORCPT + 99 others); Thu, 13 Sep 2018 15:02:12 -0400 Received: from frisell.zx2c4.com ([192.95.5.64]:44283 "EHLO frisell.zx2c4.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730619AbeIMTCL (ORCPT ); Thu, 13 Sep 2018 15:02:11 -0400 Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 83f960ba; Thu, 13 Sep 2018 13:35:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=zx2c4.com; h=mime-version :references:in-reply-to:from:date:message-id:subject:to:cc :content-type; s=mail; bh=HVtgmTjepFQpsbnrlNn210uyvC4=; b=xAgadj PEP6dkcRLdtamfJdIG+EB80RZhYGweC1qtxkl0zhMX6mfuheTkGBdAtUZlX/l4jF DBO+XponjWms25gDNOlCDA1HZ1bvt2n6WQggLE2abaGrLLMzAQAtkfMwI9u+27Tm OfiuTjG3ds9IxrLhVbZuOxt7YBP8jsuZEMos3yeH8eI9mM83yMkR0AhHAvinfFxH TpohsiWncx3bgpNbkv7WoGk8gOdr/RimpzclItAzWpaazVIReYY1k3e0CxupS6Ls Rb7m/99huGlMUZ60hrImv3NNo6ifbdGzx0IgqXgGgUTlR2NxFFSQ3ZCLISMyW/4G AMTXTL894omaJDDw== Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id e75e1bbc (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128:NO); Thu, 13 Sep 2018 13:35:39 +0000 (UTC) Received: by mail-oi0-f44.google.com with SMTP id x197-v6so9473428oix.5; Thu, 13 Sep 2018 06:52:34 -0700 (PDT) X-Gm-Message-State: APzg51D0Xy3aN1b7QgY9zb7tTmXFt8SL8laUuvyxsaTNLnELUSydRkNf +g8b0og3bRO0+B0yXjTbzuGBcdtnL65mP5KtwXY= X-Received: by 2002:aca:310b:: with SMTP id x11-v6mr6581223oix.74.1536846753360; Thu, 13 Sep 2018 06:52:33 -0700 (PDT) MIME-Version: 1.0 References: <20180911010838.8818-1-Jason@zx2c4.com> <20180911010838.8818-2-Jason@zx2c4.com> <20180912061433.GA8484@ip-172-31-15-78> <20180913050301.GA26367@ip-172-31-15-78> In-Reply-To: <20180913050301.GA26367@ip-172-31-15-78> From: "Jason A. Donenfeld" Date: Thu, 13 Sep 2018 15:52:21 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH net-next v3 01/17] asm: simd context helper API To: kevin@guarana.org, Andrew Lutomirski Cc: LKML , Netdev , David Miller , Greg Kroah-Hartman , Thomas Gleixner , Samuel Neves , linux-arch@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Sep 13, 2018 at 7:03 AM Kevin Easton wrote: > Yes. It's also how most get/put APIs already work in the kernel, eg > kref_get/put (mostly because they tend to be 'getting/putting' an > already-initialized object, though). Right; in this case the object wouldn't be initialized yet, which might defeat the purpose, since one advantage of the & way you mentioned is _put modifies the context. Andy - any opinions on this? The tl;dr is: 1) what we have now: simd_context_t simd_context = simd_get(); for (item in items) { do_something(item); simd_context = simd_relax(simd_context); } simd_put(); 2) what kevin is proposing: simd_context_t simd_context; simd_get(&simd_context); for (item in items) { do_something(item); simd_relax(&simd_context); } simd_put(&simd_context); I can see pros and cons of each approach.