Re: [Question] New mmap64 syscall?
From: Pavel Machek <hidden>
Date: 2017-01-03 21:06:25
Also in:
linux-arm-kernel, lkml
From: Pavel Machek <hidden>
Date: 2017-01-03 21:06:25
Also in:
linux-arm-kernel, lkml
quoted
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).
While I agree that batching might be good idea, I believe mmap64() makes sense, too. Yes, I guess libc could do the translation, but indirection will cost some performance, and will be problematic for stuff such as strace. ...actually, with strace and batched interface, it will be impossible to see what is going on because of races. So I'm not sure if I like the batched interface at all... Best regards, Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html