linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Russell King <linux@armlinux.org.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org
Subject: Re: [PATCH] Fix folio conversion in __dma_page_dev_to_cpu()
Date: Thu, 24 Aug 2023 18:14:38 +0100	[thread overview]
Message-ID: <89c1361e-3b0f-193f-647e-909d970cb1d1@arm.com> (raw)
In-Reply-To: <ZOeKGeAvLPBp1WVs@casper.infradead.org>

On 24/08/2023 5:49 pm, Matthew Wilcox wrote:
> On Thu, Aug 24, 2023 at 05:39:38PM +0100, Robin Murphy wrote:
>> As for >2GB segments, we've certainly seen cases of users mapping absurdly
>> large buffers and overflowing dma_length[2], so I would imagine it's only
>> the improbability of allocating that much physically-contiguous memory which
>> keeps individual segment lengths from getting up to UINT_MAX ;)
> 
> With a 32-bit kernel though?  ;-)

Oh, indeed, that's more of a challenge... I guess take an LPAE system 
with enough RAM, run VMSPLIT_3G and convince a dma-buf heap to let you 
import ~2.5GB of contiguous highmem for some kind of in-place media 
processing, maybe? Not exactly 4, but still more than 2. In principle :D

Robin.


      reply	other threads:[~2023-08-24 17:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23 19:18 Matthew Wilcox (Oracle)
2023-08-24 16:39 ` Robin Murphy
2023-08-24 16:49   ` Matthew Wilcox
2023-08-24 17:14     ` Robin Murphy [this message]

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=89c1361e-3b0f-193f-647e-909d970cb1d1@arm.com \
    --to=robin.murphy@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=linux@armlinux.org.uk \
    --cc=m.szyprowski@samsung.com \
    --cc=willy@infradead.org \
    /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