Received: by 10.213.65.68 with SMTP id h4csp861452imn; Thu, 22 Mar 2018 10:08:41 -0700 (PDT) X-Google-Smtp-Source: AG47ELuJaZ2P1TJkZYOZFqVej0LYb7jj9vQ93OKdbMF2trgpzydQAs4lUrZUq7BIvywPR3V/1DSd X-Received: by 10.99.124.25 with SMTP id x25mr18909424pgc.46.1521738521139; Thu, 22 Mar 2018 10:08:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521738521; cv=none; d=google.com; s=arc-20160816; b=rb8ptjFr8qCnj+VXyPTTizUc34pkYvkOHvA4GnzN/WEHf5XryxcFDguoLqFscistHa br9HxL7skAWW6SfmtrDTKuUUELK+/kH2YToUT0GLj88nyXfeRBml9phibEoUvWpDi3mW lg7GY0g8ZZ1kjJJXCWJAnc+CKWwjHkpAECqhb6VuK74OyssnmrZnONjSQJLVEHVvonHX R9EoMJRb+FBLZZZm8UU8KSwadox/T4u3q0RMgK4oUky1wQ+ZLWJLEIDjp+uqksTOyJMT nS22MOhFOugGNnU+cX3ayg3cT+4shXCRH8N8GJtAA/EsnaCcLAdwjYGAb92SB4lbu771 XxPQ== 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 :references:in-reply-to:mime-version:dkim-signature:dkim-signature :arc-authentication-results; bh=Ihmrspq743+rp0jqlHsc7GeiNPn1birtyQaRyIsPNaY=; b=umHezYNXijDDB6KB6xfiFfZrNTitMtPuumEDEEfs3fhg2DK0Ds7feOQdYg/1p+mO/F ToHyB0qlxHJNlV6VtBPsVJjw/YL4XmMqNqRmkJWcBvJvW86hYzUW1lG+M5K932AtCswV zpms/VZ9U4DMoGU9LG6ez9jYidgL3YatumxNi1VUTnxZ/ClRA3LmToBbFtXXa0Pvx/x0 gtLO8lP5CykhGn5yEwLjC8pMX/SMvwODJUVD3mszfmmI5C7fkwgI46idoMB9huKmpqEH sy5J9sRWva0e0seQixY9pk69jSaQw022c39u/Zfi6Mqgg6ZtX+erNntAuh+XyYShG7JB IeSg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=B1NeYvfN; dkim=fail header.i=@linux-foundation.org header.s=google header.b=TJLhG7Um; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f186si3763842pgc.527.2018.03.22.10.08.25; Thu, 22 Mar 2018 10:08:41 -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=fail header.i=@gmail.com header.s=20161025 header.b=B1NeYvfN; dkim=fail header.i=@linux-foundation.org header.s=google header.b=TJLhG7Um; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751752AbeCVRH0 (ORCPT + 99 others); Thu, 22 Mar 2018 13:07:26 -0400 Received: from mail-io0-f171.google.com ([209.85.223.171]:44307 "EHLO mail-io0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751595AbeCVRHZ (ORCPT ); Thu, 22 Mar 2018 13:07:25 -0400 Received: by mail-io0-f171.google.com with SMTP id h23so11823344iob.11; Thu, 22 Mar 2018 10:07:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=Ihmrspq743+rp0jqlHsc7GeiNPn1birtyQaRyIsPNaY=; b=B1NeYvfNS0OpZpNwmx4i1b/6S8yEPzCeH3baNH7etbPcfuu7KhWa8g8VSVH8dXpu1n OAlc4kBweNHd4dE5PNXpJECcQcdu+MCaA7tElhPY1E307Q6DAw7jwqdFvM6kyOQyhkuW gREJpS3P9B9VXQzDG9W0JEFS5TBQTiQQxgTbrPSsMf5VAaHMlyEMEmtvwTXcx0+OJ5jj M0138TlQb7Z+Xf1a/B1sEU4dvxbh3KNGF4VDL3FZL3cYUbpcyf6N5ASrEAGzFycCYj8K oG1XL/V71c5rMRzzOpwudzy+DHkF/YmfFQAUHLI8CJJ/x2wtF9/wdxJ8zu97q4WY0Elz 804w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=Ihmrspq743+rp0jqlHsc7GeiNPn1birtyQaRyIsPNaY=; b=TJLhG7UmKpW9mSXFDX9lQh6Yb9gTVw1RssY5UMix5NsaH4PyhTOWgIOCoAwQ0cfdxg LtUGKdy5ui01/dE/75DWF872I/ScStxqfLf4k7JQwhWqlHQ3SQA2xtMBcvZvrFo3gPqR DNhWFimOeW5hfJsvy+HjET4oKv6fE2wyRQ7B4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=Ihmrspq743+rp0jqlHsc7GeiNPn1birtyQaRyIsPNaY=; b=JZs4OThKtC9BaaHoXKl64+Has5aPnBAWpMDdksqBQzUbcENx1fmM8oOwG6Qo2Z4iK+ 8kQIdxY88EU2H2zaFSJhZ9oZSTqUhzXrpSVQ2zCLJW4j4ZggQZDhiCpIBZC50j5dr7vW xZbv7SHWMmFRJrxYq37GKw6fPskMcouNTRbLOOo6kWszR9i6cW/GJqrw8Bk36+hAyRGW uVpZB1pPynqqSqbpjrifqZckJmh2iywNDmM+RsFT1Q0Idbr7A3v+bbZxn2jYC70S5bZp F4vr49KEsGxR30Mgpv86lqv3swtkZiC2xD6tf8UI7+rIcvyLLz1V3bYQLEXQiBQ4eHli Eqsw== X-Gm-Message-State: AElRT7HFkYOlSdawBbkvFcr/MzosuZ5x6PvrhUyuanklLakG5BCxtVAb r78dH+H0KSs/CYYePHMPnaEKW+keBMqwxlTNIz0= X-Received: by 10.107.182.214 with SMTP id g205mr27904523iof.203.1521738444451; Thu, 22 Mar 2018 10:07:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.95.15 with HTTP; Thu, 22 Mar 2018 10:07:23 -0700 (PDT) In-Reply-To: References: <7f0ddb3678814c7bab180714437795e0@AcuMS.aculab.com> <7f8d811e79284a78a763f4852984eb3f@AcuMS.aculab.com> <20180320082651.jmxvvii2xvmpyr2s@gmail.com> <20180321074634.dzpyjz3ia46snodh@gmail.com> <2f5cb27711e741fba77846574e72eb62@AcuMS.aculab.com> From: Linus Torvalds Date: Thu, 22 Mar 2018 10:07:23 -0700 X-Google-Sender-Auth: xI78y8ATaJJI0gbg7tAJY_cshEI Message-ID: Subject: Re: [RFC PATCH 0/3] kernel: add support for 256-bit IO access To: David Laight Cc: Ingo Molnar , Thomas Gleixner , Rahul Lakkireddy , "x86@kernel.org" , "linux-kernel@vger.kernel.org" , "netdev@vger.kernel.org" , "mingo@redhat.com" , "hpa@zytor.com" , "davem@davemloft.net" , "akpm@linux-foundation.org" , "ganeshgr@chelsio.com" , "nirranjan@chelsio.com" , "indranil@chelsio.com" , Andy Lutomirski , Peter Zijlstra , Fenghua Yu , Eric Biggers 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, Mar 22, 2018 at 5:48 AM, David Laight wrote: > > So if we needed to do PIO reads using the AVX2 (or better AVX-512) > registers would make a significant difference. > Fortunately we can 'dma' most of the data we need to transfer. I think this is the really fundamental issue. A device that expects PIO to do some kind of high-performance transaction is a *broken* device. It really is that simple. We don't bend over for misdesigned hardware crap unless it is really common. > I've traced writes before, they are a lot faster and are limited > by things in the fpga fabric (they appear back to back). The write combine buffer really should be much more effective than any AVX or similar can ever be. Linus