Linux filesystem development
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Amir Goldstein <amir73il@gmail.com>, Miklos Szeredi <miklos@szeredi.hu>
Cc: fuse-devel <fuse-devel@lists.linux.dev>,
	linux-fsdevel@vger.kernel.org, John Groves <John@groves.net>,
	Joanne Koong <joannelkoong@gmail.com>,
	"Darrick J . Wong" <djwong@kernel.org>,
	Bernd Schubert <bernd@bsbernd.com>,
	Horst Birthelmer <horst@birthelmer.de>,
	Luis Henriques <luis@igalia.com>
Subject: Re: [post LSFMM summary] where is fuse going?
Date: Wed, 13 May 2026 14:57:58 +0800	[thread overview]
Message-ID: <fe714fbc-c9a5-4c26-8b7d-6976adb56b63@linux.alibaba.com> (raw)
In-Reply-To: <CAOQ4uxiTowEnpQR3-oBXM3Q5uxBf5PXeNu+Qda8CVeD0fTHfXg@mail.gmail.com>



On 2026/5/13 05:40, Amir Goldstein wrote:
> On Tue, May 12, 2026 at 12:01 PM Miklos Szeredi <miklos@szeredi.hu> wrote:
>>
>> On Tue, 12 May 2026 at 09:53, Amir Goldstein <amir73il@gmail.com> wrote:
>>
>>> The problem is only with  fuse_passthrough_mmap().
>>> Depending on the workload (?) mmap may not be important and
>>> we could fail if trying to map cross-backing-id regions.
>>
>> mmap(2) is the main entry point into famfs,  so it's very important.
>>
>> That doesn't work with "traditional" passthrough and needs to do the
>> DAX mapping that famfs currently does.
>>
> 
> Yes, famfs surely needs mmap to multiple daxdev and this is done.
> 
> I was referring to Gao's question about dealing with non-dax multi
> backing id (const mapped) files.

Yes, it can work on DAX and my question was all about
mmap backed by multiple pagecache-backed files.

Thanks,
Gao Xiang

> 
> Thanks,
> Amir.


  reply	other threads:[~2026-05-13  6:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 15:12 [post LSFMM summary] where is fuse going? Miklos Szeredi
2026-05-11 16:43 ` Luis Henriques
2026-05-11 19:17   ` Horst Birthelmer
2026-05-12  8:46     ` Luis Henriques
2026-05-12  9:57       ` Miklos Szeredi
2026-05-12  9:38   ` Miklos Szeredi
2026-05-11 17:18 ` Amir Goldstein
2026-05-12  3:20   ` Gao Xiang
2026-05-12  7:53     ` Amir Goldstein
2026-05-12 10:00       ` Miklos Szeredi
2026-05-12 21:40         ` Amir Goldstein
2026-05-13  6:57           ` Gao Xiang [this message]
2026-05-12  9:52   ` Miklos Szeredi
2026-05-12 20:33     ` Darrick J. Wong
2026-05-12 20:23 ` Darrick J. Wong

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=fe714fbc-c9a5-4c26-8b7d-6976adb56b63@linux.alibaba.com \
    --to=hsiangkao@linux.alibaba.com \
    --cc=John@groves.net \
    --cc=amir73il@gmail.com \
    --cc=bernd@bsbernd.com \
    --cc=djwong@kernel.org \
    --cc=fuse-devel@lists.linux.dev \
    --cc=horst@birthelmer.de \
    --cc=joannelkoong@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=luis@igalia.com \
    --cc=miklos@szeredi.hu \
    /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