mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-kernel@vger.kernel.org, fuse-devel@lists.sourceforge.net,
	akpm@linux-foundation.org, npiggin@suse.de
Subject: Re: [PATCH 4/4] FUSE: implement direct mmap
Date: Thu, 09 Jul 2009 08:14:50 +0900	[thread overview]
Message-ID: <4A55286A.6040202@kernel.org> (raw)
In-Reply-To: <E1MNmZM-0001ZB-GR@pomaz-ex.szeredi.hu>

Hello, Miklos.

Miklos Szeredi wrote:
> On Sat, 04 Jul 2009, Tejun Heo wrote:
>>> Afaics sound drivers now map the dma memory with remap_pfn_range().
>>> Similary we could allocate a chunk of non-swapabble kernel memory on
>>> request from the userspace server and map its pages using this trick
>>> to both the server's and the client's address space.
>>>
>>> This is still sort of OSSP specific, I don't see clearly how it could
>>> be made more generic.
>> Using non-swappable memory would be fine for most device emulations
>> but mapping large amount of pages would be problematic.  Hmmm... this
>> is difficult.  It's a compromise among flexibility, scalability and
>> code complexity.
> 
> What's the difficulty?

The desire to avoid pinning all the mapped pages.  :-)

> Allocating pages, giving them an ID and mapping them into various page
> tables seems simple in contrast to trying to make a tmpfs file be a
> fuse file at the same time, which the VM is really not prepared for.

If pinning all the pages are okay, the above should work fine.

Thanks.

-- 
tejun

  reply	other threads:[~2009-07-08 23:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18  9:24 [PATCHSET] FUSE/CUSE: implement direct mmap, take#3 Tejun Heo
2009-06-18  9:24 ` [PATCH 1/4] fdtable: export alloc_fd() Tejun Heo
2009-06-24  4:39   ` Al Viro
2009-06-30  3:05     ` Tejun Heo
2009-06-18  9:24 ` [PATCH 2/4] FUSE: make request_wait_answer() wait for ->end() completion Tejun Heo
     [not found]   ` <20090623165354.073a61fe.akpm@linux-foundation.org>
2009-06-24  0:04     ` Tejun Heo
2009-06-24 10:02   ` Miklos Szeredi
2009-06-29 16:20     ` Tejun Heo
2009-06-18  9:24 ` [PATCH 3/4] FUSE: implement fuse_req->prep() Tejun Heo
2009-06-23 23:56   ` Andrew Morton
2009-06-24  0:07     ` Tejun Heo
2009-06-18  9:24 ` [PATCH 4/4] FUSE: implement direct mmap Tejun Heo
2009-06-24  0:14   ` Andrew Morton
2009-06-29 16:59     ` Tejun Heo
2009-06-24 10:33   ` Miklos Szeredi
2009-06-29 16:42     ` Tejun Heo
2009-07-02 13:51       ` Miklos Szeredi
2009-07-04 11:14         ` Tejun Heo
2009-07-06 11:41           ` Miklos Szeredi
2009-07-08 23:14             ` Tejun Heo [this message]
2009-07-09 10:35               ` Miklos Szeredi
2009-06-18  9:27 ` [PATCH libfuse] implement direct mmap support Tejun Heo

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=4A55286A.6040202@kernel.org \
    --to=tj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=npiggin@suse.de \
    /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

Powered by JetHome