From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935806AbdAJKzZ (ORCPT ); Tue, 10 Jan 2017 05:55:25 -0500 Received: from mout.kundenserver.de ([212.227.17.13]:61992 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964944AbdAJKzX (ORCPT ); Tue, 10 Jan 2017 05:55:23 -0500 From: Arnd Bergmann To: Christoph Hellwig Cc: Nikita Yushchenko , linux-arm-kernel@lists.infradead.org, Catalin Marinas , Will Deacon , linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org, Simon Horman , linux-pci@vger.kernel.org, Bjorn Helgaas , artemi.ivanov@cogentembedded.com, Keith Busch , Jens Axboe , Sagi Grimberg , linux-nvme@lists.infradead.org Subject: Re: NVMe vs DMA addressing limitations Date: Tue, 10 Jan 2017 11:54:26 +0100 Message-ID: <1967203.EWsxCL11oI@wuerfel> User-Agent: KMail/5.1.3 (Linux/4.4.0-34-generic; KDE/5.18.0; x86_64; ; ) In-Reply-To: <20170110070719.GA17208@lst.de> References: <1483044304-2085-1-git-send-email-nikita.yoush@cogentembedded.com> <20170110070719.GA17208@lst.de> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:WMdY9yn6g2EbvWUkCSQ0IcmynrzydaYLptwjyK4p0P+77v6OZvX vYQhdAv3Y5aO4ZNuLj5kEgOuCQ8H/A/e/Yh6moqR3ZF/0wqSpqJBAARVsJPV3dZyELLJutG E8n9Vai6xSsVZEQRc6A88voNpvW3JceDTP3Usj+d+4DcRlB+RGZ92WBSMXfo2ELY72C0Zyc yoii4HIjp6G0lEeKsz4Hw== X-UI-Out-Filterresults: notjunk:1;V01:K0:c/dea9UKXVg=:D6Nt+0bhvT6MqHWUHhfDVT PE9o5ErjU8OcfDZC64JzXq5H2xVSYIIKySgbhZjyEm4U5Dp1cEHwwPV61xCeSeKHbAex39+vZ ZKcpppcnrjaZ5ZkntzImFZWMA0zcAiYkj6g+kJcFkU2y08b62t7Wea2o4mrox1nVU22j8HSPs TE27piAMecAyZeboKYud/ziUIng6mkSmTtq36Q0d8SMdTge7apTRajCW5crTwRDA4M67j54Sk WO5uE0KH+sQilhar4v8Bay8xve2Ew+7Czhl0bvadUBEPhmRkk4+O5GR4rjuNhOuWxzOuImizh ebX+JptLeyF48eYdaXxjW2ufbE8Aq0SaS7sk3sGNuIU2YcCl+DzoNos+oSbmrDJJHpFhW//uL AsTe/lj0D8d8qkX3Q+fmXXTsfmc+5LZOmXDQz4hKTH669NJ599OpdFtR0QJg1+4cRjIk0EFwh fx8PMvhsk5wfl5COv0k7AFaz/HYJGlvfiEhjzqBa81qUlxGKiT2jROELGFYpR6bIYsQDBvS5P Vv4ZHBnwpYOCKG9ni1fQ9Yxn6AMipOyOJDwpCgoMNMUuQucehkUzRPWoU0uG2BmQSD/IeUDQt Mc6R9uONmfX7z7mWUcE6YYcYLkDfSL5nMrvrCFMW1eUF7rXG4EMm5ab5UKA3ajp0O3z/Q5Ric 5IUo6PT0lbEkY2TqyTCyECY+PyEK1iWm8q3eAWAi6JlmtcSuEPgSNNF+HxX0P0zvgwfJ/EX3r 5ni4Yzc9enSW+D3g Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday, January 10, 2017 8:07:20 AM CET Christoph Hellwig wrote: > On Tue, Jan 10, 2017 at 09:47:21AM +0300, Nikita Yushchenko wrote: > > I'm now working with HW that: > > - is now way "low end" or "obsolete", it has 4G of RAM and 8 CPU cores, > > and is being manufactured and developed, > > - has 75% of it's RAM located beyond first 4G of address space, > > - can't physically handle incoming PCIe transactions addressed to memory > > beyond 4G. > > It might not be low end or obselete, but it's absolutely braindead. > Your I/O performance will suffer badly for the life of the platform > because someone tries to save 2 cents, and there is not much we can do > about it. Unfortunately it is a common problem for arm64 chips that were designed by taking a 32-bit SoC and replacing the CPU core. The swiotlb is the right workaround for this, and I think we all agree that we should just make it work correctly. Arnd