[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160526.124344.1660236473079504674.davem@davemloft.net>
Date: Thu, 26 May 2016 12:43:44 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: catalin.marinas@....com
Cc: arnd@...db.de, ynorov@...iumnetworks.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, linux-arch@...r.kernel.org,
linux-s390@...r.kernel.org, libc-alpha@...rceware.org,
schwidefsky@...ibm.com, heiko.carstens@...ibm.com,
pinskia@...il.com, broonie@...nel.org, joseph@...esourcery.com,
christoph.muellner@...obroma-systems.com,
bamvor.zhangjian@...wei.com, szabolcs.nagy@....com,
klimov.linux@...il.com, Nathan_Lynch@...tor.com, agraf@...e.de,
Prasun.Kapoor@...iumnetworks.com, kilobyte@...band.pl,
geert@...ux-m68k.org, philipp.tomsich@...obroma-systems.com
Subject: Re: [PATCH 01/23] all: syscall wrappers: add documentation
From: Catalin Marinas <catalin.marinas@....com>
Date: Thu, 26 May 2016 15:20:58 +0100
> We can solve (a) by adding more __SC_WRAP annotations in the generic
> unistd.h.
...
I really think it's much more robust to clear the tops of the registers
by default. Then you won't be auditing constantly and adding more and
more wrappers.
You can't even quantify the performance gains for me in any precise
way. Whatever you gain by avoiding the 64-bit
decompostion/reconstitution for those few system calls with 64-bit
registers, you are losing by calling the wrappers for more common
system calls, more often.
"it's more natural to pass 64-bit values in a register" is not a clear
justification for this change.
This looks way over engineered to me.
Powered by blists - more mailing lists