public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Pantelis Antoniou <p.antoniou@partner.samsung.com>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
	Artem Krupotkin <artem.k@samsung.com>,
	Charles Briere <c.briere@samsung.com>,
	Wade Farnsworth <wade.farnsworth@siemens.com>
Subject: Re: [PATCH 0/1] Fix zero copy I/O on __get_user_pages allocated pages
Date: Wed, 7 May 2025 14:50:18 -0700	[thread overview]
Message-ID: <20250507145018.385c0a090a0d61c06e985ad9@linux-foundation.org> (raw)
In-Reply-To: <20250507154105.763088-1-p.antoniou@partner.samsung.com>

On Wed, 7 May 2025 10:41:04 -0500 Pantelis Antoniou <p.antoniou@partner.samsung.com> wrote:

> Updates to network filesystems enabled zero copy I/O by using the
> netfslib common accessors.

Updates by whom?  Are all the people who need to know about this being
cc'ed here?

> One example of that is the 9p filesystem which is commonly used in qemu
> based setups for sharing files with the host.
> 
> In our emulation environment we have noticed failing writes when performing
> I/O from a userspace mapped DRM GEM buffer object.
> The platform does not use VRAM, all graphics memory is regular DRAM memory,
> allocated via __get_free_pages

We should identify which kernel version(s) should be patched, please. 
6.16-rc1?  6.15?  -stable?

I often make these decisions but in this case I have far too little
information to be able to do that.

Thanks.


  parent reply	other threads:[~2025-05-07 21:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250507154119uscas1p2a4055d14ab111fdb94a6378789c38d9d@uscas1p2.samsung.com>
2025-05-07 15:41 ` [PATCH 0/1] Fix zero copy I/O on __get_user_pages allocated pages Pantelis Antoniou
2025-05-07 15:41   ` [PATCH 1/1] " Pantelis Antoniou
2025-05-08 15:03     ` David Hildenbrand
2025-05-08 15:23       ` Pantelis Antoniou
2025-05-08 15:37         ` David Hildenbrand
2025-05-08 15:47           ` Pantelis Antoniou
2025-05-07 21:50   ` Andrew Morton [this message]
2025-05-08  8:24     ` [PATCH 0/1] " Pantelis Antoniou
2025-05-07 21:54   ` Andrew Morton

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=20250507145018.385c0a090a0d61c06e985ad9@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=artem.k@samsung.com \
    --cc=c.briere@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=p.antoniou@partner.samsung.com \
    --cc=wade.farnsworth@siemens.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