From: Florian Weimer <fweimer@redhat.com>
To: Yury Norov <ynorov@caviumnetworks.com>
Cc: libc-alpha@sourceware.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
szabolcs.nagy@arm.com, heiko.carstens@de.ibm.com,
cmetcalf@ezchip.com, philipp.tomsich@theobroma-systems.com,
joseph@codesourcery.com, zhouchengming1@huawei.com,
Prasun.Kapoor@caviumnetworks.com, agraf@suse.de,
geert@linux-m68k.org, kilobyte@angband.pl,
manuel.montezelo@gmail.com, arnd@arndb.de, pinskia@gmail.com,
linyongting@huawei.com, klimov.linux@gmail.com,
broonie@kernel.org, bamvor.zhangjian@huawei.com,
linux-arm-kernel@lists.infradead.org, maxim.kuvyrkov@linaro.org,
Nathan_Lynch@mentor.com, schwidefsky@de.ibm.com,
davem@davemloft.net, christoph.muellner@theobroma-systems.com
Subject: Re: [Question] New mmap64 syscall?
Date: Thu, 8 Dec 2016 16:47:34 +0100 [thread overview]
Message-ID: <14981df2-b120-17c3-a5a8-5cbbd2008c4f@redhat.com> (raw)
Message-ID: <20161208154734.XHiRkwEF1WeX4VtE-QKB9kxwrPIqIv8RRF9RrbriG2w@z> (raw)
In-Reply-To: <20161207154811.GA15248@yury-N73SV>
On 12/07/2016 04:48 PM, Yury Norov wrote:
> On Wed, Dec 07, 2016 at 02:23:55PM +0100, Florian Weimer wrote:
>> On 12/06/2016 07:54 PM, Yury Norov wrote:
>>> 3. Introduce new mmap64() syscall like this:
>>> sys_mmap64(void *addr, size_t len, int prot, int flags, int fd, struct off_pair *off);
>>> (The pointer here because otherwise we have 7 args, if simply pass off_hi and
>>> off_lo in registers.)
>>
>> I would prefer a batched mmap/munmap/mremap/mprotect/madvise interface, so
>> that VM changes can be coalesced and the output reduced. This interface
>> could then be used to implement mmap on 32-bit architectures as well because
>> the offset restrictions would not apply there.
>
> Hi Florian,
>
> I frankly don't understand what you mean, All syscalls you mentioned
> doesn't take off_t or other 64-bit arguments. 'VM changes' - virtual
> memory? If so, I don't see any changes in VM with this approach, just
> correct handling of big offsets.
What I was trying to suggest is a completely different interface which
is not subject to register size constraints and which has been requested
before (a mechanism for batching mm updates).
Thanks,
Florian
next prev parent reply other threads:[~2016-12-08 15:54 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 18:54 [Question] New mmap64 syscall? Yury Norov
2016-12-06 18:54 ` Yury Norov
2016-12-06 21:20 ` Arnd Bergmann
2016-12-07 10:34 ` Yury Norov
2016-12-07 10:34 ` Yury Norov
2016-12-07 11:07 ` Dr. Philipp Tomsich
2016-12-07 12:39 ` Yury Norov
2016-12-07 16:32 ` Catalin Marinas
2016-12-07 16:32 ` Catalin Marinas
2016-12-07 16:43 ` Dr. Philipp Tomsich
2016-12-07 16:43 ` Dr. Philipp Tomsich
2016-12-07 21:30 ` Arnd Bergmann
2016-12-07 21:30 ` Arnd Bergmann
2016-12-10 9:10 ` Pavel Machek
2016-12-10 9:10 ` Pavel Machek
2016-12-10 9:21 ` Pavel Machek
2016-12-10 9:21 ` Pavel Machek
2016-12-11 12:56 ` Yury Norov
2016-12-11 12:56 ` Yury Norov
2016-12-11 12:56 ` [PATCH 1/3] mm: move argument checkers of mmap_pgoff() to separated routine Yury Norov
2016-12-11 12:56 ` Yury Norov
2016-12-11 12:56 ` [PATCH 2/3] sys_mmap64() Yury Norov
2016-12-11 12:56 ` Yury Norov
2016-12-11 14:48 ` kbuild test robot
2016-12-11 14:48 ` kbuild test robot
2016-12-11 14:56 ` kbuild test robot
2016-12-11 14:56 ` kbuild test robot
2016-12-11 12:56 ` [PATCH 3/3] mm: make pagoff_t type 64-bit Yury Norov
2016-12-11 12:56 ` Yury Norov
2016-12-11 13:31 ` kbuild test robot
2016-12-11 13:31 ` kbuild test robot
2016-12-11 13:41 ` kbuild test robot
2016-12-11 13:41 ` kbuild test robot
2016-12-11 14:59 ` Arnd Bergmann
2016-12-11 14:59 ` Arnd Bergmann
2016-12-16 10:55 ` Yury Norov
2016-12-16 10:55 ` Yury Norov
2016-12-16 11:02 ` Arnd Bergmann
2016-12-16 11:02 ` Arnd Bergmann
2016-12-18 9:23 ` Christoph Hellwig
2016-12-18 9:23 ` Christoph Hellwig
2016-12-07 13:23 ` [Question] New mmap64 syscall? Florian Weimer
2016-12-07 13:23 ` Florian Weimer
2016-12-07 15:48 ` Yury Norov
2016-12-07 15:48 ` Yury Norov
2016-12-08 15:47 ` Florian Weimer [this message]
2016-12-08 15:47 ` Florian Weimer
2017-01-03 20:54 ` Pavel Machek
2017-01-03 20:54 ` Pavel Machek
2017-01-12 16:13 ` Florian Weimer
2017-01-12 16:13 ` Florian Weimer
2017-01-12 21:51 ` Pavel Machek
2017-01-12 21:51 ` Pavel Machek
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=14981df2-b120-17c3-a5a8-5cbbd2008c4f@redhat.com \
--to=fweimer@redhat.com \
--cc=Nathan_Lynch@mentor.com \
--cc=Prasun.Kapoor@caviumnetworks.com \
--cc=agraf@suse.de \
--cc=arnd@arndb.de \
--cc=bamvor.zhangjian@huawei.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=christoph.muellner@theobroma-systems.com \
--cc=cmetcalf@ezchip.com \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=heiko.carstens@de.ibm.com \
--cc=joseph@codesourcery.com \
--cc=kilobyte@angband.pl \
--cc=klimov.linux@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linyongting@huawei.com \
--cc=manuel.montezelo@gmail.com \
--cc=maxim.kuvyrkov@linaro.org \
--cc=philipp.tomsich@theobroma-systems.com \
--cc=pinskia@gmail.com \
--cc=schwidefsky@de.ibm.com \
--cc=szabolcs.nagy@arm.com \
--cc=ynorov@caviumnetworks.com \
--cc=zhouchengming1@huawei.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;
as well as URLs for NNTP newsgroup(s).