From: Jason Gunthorpe <jgg@nvidia.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: John Hubbard <jhubbard@nvidia.com>,
Gal Pressman <galpress@amazon.com>,
Daniel Vetter <daniel@ffwll.ch>,
Sumit Semwal <sumit.semwal@linaro.org>,
Doug Ledford <dledford@redhat.com>,
"open list:DMA BUFFER SHARING FRAMEWORK"
<linux-media@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-rdma <linux-rdma@vger.kernel.org>,
Oded Gabbay <ogabbay@habana.ai>, Tomer Tayar <ttayar@habana.ai>,
Yossi Leybovich <sleybo@amazon.com>,
Alexander Matushevsky <matua@amazon.com>,
Leon Romanovsky <leonro@nvidia.com>,
Jianxin Xiong <jianxin.xiong@intel.com>
Subject: Re: [RFC] Make use of non-dynamic dmabuf in RDMA
Date: Wed, 25 Aug 2021 09:38:02 -0300 [thread overview]
Message-ID: <20210825123802.GD1721383@nvidia.com> (raw)
In-Reply-To: <fa22a1f9-fee6-21ea-3377-3ba99e9eb309@amd.com>
On Wed, Aug 25, 2021 at 02:27:08PM +0200, Christian König wrote:
> Am 25.08.21 um 14:18 schrieb Jason Gunthorpe:
> > On Wed, Aug 25, 2021 at 08:17:51AM +0200, Christian König wrote:
> >
> > > The only real option where you could do P2P with buffer pinning are those
> > > compute boards where we know that everything is always accessible to
> > > everybody and we will never need to migrate anything. But even then you want
> > > some mechanism like cgroups to take care of limiting this. Otherwise any
> > > runaway process can bring down your whole system.
> > Why? It is not the pin that is the problem, it was allocating GPU
> > dedicated memory in the first place. pinning it just changes the
> > sequence to free it. No different than CPU memory.
>
> Pinning makes the memory un-evictable.
>
> In other words as long as we don't pin anything we can support as many
> processes as we want until we run out of swap space. Swapping sucks badly
> because your applications become pretty much unuseable, but you can easily
> recover from it by killing some process.
>
> With pinning on the other hand somebody sooner or later receives an -ENOMEM
> or -ENOSPC and there is no guarantee that this goes to the right process.
It is not really different - you have the same failure mode once the
system runs out of swap.
This is really the kernel side trying to push a policy to the user
side that the user side doesn't want..
Dedicated systems are a significant use case here and should be
supported, even if the same solution wouldn't be applicable to someone
running a desktop.
Jason
next prev parent reply other threads:[~2021-08-25 12:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 7:43 [RFC] Make use of non-dynamic dmabuf in RDMA Gal Pressman
2021-08-18 8:00 ` Christian König
2021-08-18 8:37 ` Gal Pressman
2021-08-18 9:34 ` Daniel Vetter
2021-08-19 23:06 ` Jason Gunthorpe
2021-08-20 7:25 ` Daniel Vetter
2021-08-20 12:33 ` Jason Gunthorpe
2021-08-20 12:58 ` Gal Pressman
2021-08-20 14:32 ` Jason Gunthorpe
2021-08-21 9:16 ` Gal Pressman
2021-08-23 10:43 ` Christian König
2021-08-24 9:06 ` Gal Pressman
2021-08-24 9:32 ` Christian König
2021-08-24 17:27 ` John Hubbard
2021-08-24 17:32 ` Jason Gunthorpe
2021-08-24 17:35 ` John Hubbard
2021-08-24 19:15 ` Dave Airlie
2021-08-24 19:30 ` Jason Gunthorpe
2021-08-24 19:43 ` Alex Deucher
2021-08-24 20:00 ` Xiong, Jianxin
2021-08-25 6:17 ` Christian König
2021-08-25 6:47 ` John Hubbard
2021-08-25 12:18 ` Jason Gunthorpe
2021-08-25 12:27 ` Christian König
2021-08-25 12:38 ` Jason Gunthorpe [this message]
2021-08-25 13:51 ` Christian König
2021-08-25 14:47 ` Jason Gunthorpe
2021-08-25 15:14 ` Christian König
2021-08-25 15:49 ` Jason Gunthorpe
2021-08-25 16:02 ` Oded Gabbay
2021-09-01 11:20 ` Gal Pressman
2021-09-01 11:24 ` Christian König
2021-09-02 6:56 ` Gal Pressman
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=20210825123802.GD1721383@nvidia.com \
--to=jgg@nvidia.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dledford@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=galpress@amazon.com \
--cc=jhubbard@nvidia.com \
--cc=jianxin.xiong@intel.com \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=matua@amazon.com \
--cc=ogabbay@habana.ai \
--cc=sleybo@amazon.com \
--cc=sumit.semwal@linaro.org \
--cc=ttayar@habana.ai \
/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;
as well as URLs for NNTP newsgroup(s).