From: Logan Gunthorpe <lsgunthorpe@gmail.com>
To: D Meyer <dmeyer@gigaio.com>
Cc: Serge Semin <fancer.lancer@gmail.com>,
linux-ntb <linux-ntb@googlegroups.com>
Subject: Re: Is the Scratchpad Implementation Using a LUT Standard?
Date: Thu, 12 Oct 2017 12:38:35 -0600 [thread overview]
Message-ID: <bcccee97-cb4c-7d8a-c55d-c17d09972c1e@gmail.com> (raw)
In-Reply-To: <CA+GK6ekKuvkzLod=LJ4+MqVH0MTKwyQTcvOpUEzfBAjkGeYyBg@mail.gmail.com>
On 12/10/17 12:31 PM, D Meyer wrote:
> Imagine accessing PiB of storage that uses memory semantics (early
> last year PCI-SIG noted a vendor selling an endpoint capable of 2 TB),
> a sea of GPGPU cards, etc. in a heterogeneous cloud computing
> environment, and wanting to control access to windows of that stuff
> being used by multiple applications running in one or more hosts. A
> small number of windows are not sufficient. LUTs provide a good method
> for being able to establish long-lasting as well as ephemeral
> translations and, in conjunction with IOMMU, PCIe's ACS, etc. as well
> as various QoS features could provide a good start on data protection
> and client performance.
>
> This much bigger than ntb_transport to support networks with some
> NVMe drives and GPU endpoints. Fun!
>
> LUTs aren't an afterthought. I think they're really valuable.
See my comment in my previous email. Until there's some published code
(preferably upstream) that uses them it's not worth assuming what those
uses might be and giving yourself arbitrary restrictions that may never
come
to pass. The market may never even want what you are imagining.
Logan
next prev parent reply other threads:[~2017-10-12 18:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 12:57 Is the Scratchpad Implementation Using a LUT Standard? Doug Meyer
2017-10-10 14:17 ` Allen Hubbe
2017-10-10 15:52 ` Doug Meyer
2017-10-11 16:19 ` lsgunthorpe
2017-10-11 17:41 ` Serge Semin
2017-10-11 18:03 ` Logan Gunthorpe
2017-10-12 18:31 ` D Meyer
2017-10-12 18:38 ` Logan Gunthorpe [this message]
2017-10-11 18:23 ` D Meyer
2017-10-11 18:44 ` Logan Gunthorpe
2017-10-12 18:05 ` D Meyer
2017-10-12 18:33 ` Logan Gunthorpe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bcccee97-cb4c-7d8a-c55d-c17d09972c1e@gmail.com \
--to=lsgunthorpe@gmail.com \
--cc=dmeyer@gigaio.com \
--cc=fancer.lancer@gmail.com \
--cc=linux-ntb@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox