linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Dr. Philipp Tomsich" <philipp.tomsich@theobroma-systems.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Yury Norov <ynorov@caviumnetworks.com>,
	libc-alpha@sourceware.org, linux-arch@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	szabolcs.nagy@arm.com, heiko.carstens@de.ibm.com,
	cmetcalf@ezchip.com, "Joseph S. Myers" <joseph@codesourcery.com>,
	zhouchengming1@huawei.com, "Kapoor,
	Prasun" <Prasun.Kapoor@caviumnetworks.com>,
	Alexander Graf <agraf@suse.de>,
	geert@linux-m68k.org, kilobyte@angband.pl,
	manuel.montezelo@gmail.com, Andrew Pinski <pinskia@gmail.com>,
	linyongting@huawei.com, Alexey Klimov <klimov.linux@gmail.com>,
	broonie@kernel.org,
	"Zhangjian (Bamvor)" <bamvor.zhangjian@huawei.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
	Nathan Lynch <Nathan_Lynch@mentor.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	davem@davemloft.net, christoph.muellner@theobroma-systems.com
Subject: Re: [Question] New mmap64 syscall?
Date: Sat, 10 Dec 2016 10:10:01 +0100	[thread overview]
Message-ID: <20161210091001.GA17896@xo-6d-61-c0.localdomain> (raw)
Message-ID: <20161210091001.9kgN2NA8KJadUjxap5_GAcru_CXkVlPgPr0U6ehkK0k@z> (raw)
In-Reply-To: <12011325.PfzMMUCfyS@wuerfel>

Hi!

> > Most of these advantages should eventually go away, when struct-reorg makes
> > it way into the compiler. That said, it’s a marginal (but real) improvement for a
> > subset of SPEC.
> > 
> > In the real world, the importance of ILP32 as an aid to transition legacy code
> > that is not 64bit clean… and this should drive the ILP32 discussion. That we
> > get a boost in our SPEC scores is just a nice extra that we get from it 
> 
> To bring this back from the philosophical questions of ABI design
> to the specific point of what file offset width you want for mmap()
> on 32-bit architectures.
> 
> For all I can tell, using mmap() to access a file that is many thousand
> times larger than your virtual address space is completely crazy.

Dunno. Wanting to mmap part of a partition does not seem too crazy... I'm pretty
sure there's some tool out there that uses mmap(), just because mmap() was nicer
to use then read(). And when the partition is big, the offset may be big.

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2016-12-10 15:18 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 [this message]
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
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=20161210091001.GA17896@xo-6d-61-c0.localdomain \
    --to=pavel@ucw.cz \
    --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).