From: Borislav Petkov <bp@alien8.de>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org, x86@kernel.org,
linux@rasmusvillemoes.dk, torvalds@linux-foundation.org
Subject: Re: [RFC] Improve memset
Date: Sat, 14 Sep 2019 13:39:41 +0200 [thread overview]
Message-ID: <20190914113941.GB28054@zn.tnic> (raw)
In-Reply-To: <20190914092915.GA17409@avx2>
On Sat, Sep 14, 2019 at 12:29:15PM +0300, Alexey Dobriyan wrote:
> eh... I'd just drop it. These registers screw up everything.
The intent is to not touch memset_orig and let it die with its users. It
is irrelevant now anyway.
If it can be shown that the extended list of clobbered registers hurt
performance, then we can improve it for the sake of keeping register
pressure low.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2019-09-14 11:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-14 9:29 [RFC] Improve memset Alexey Dobriyan
2019-09-14 11:39 ` Borislav Petkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-13 7:22 Borislav Petkov
2019-09-13 7:35 ` Ingo Molnar
2019-09-13 7:50 ` Borislav Petkov
2019-09-13 8:51 ` Rasmus Villemoes
2019-09-13 9:00 ` Linus Torvalds
2019-09-13 9:18 ` Rasmus Villemoes
2019-09-13 10:42 ` Borislav Petkov
2019-09-13 16:36 ` Borislav Petkov
2019-09-16 9:18 ` Rasmus Villemoes
2019-09-16 17:25 ` Linus Torvalds
2019-09-16 17:40 ` Andy Lutomirski
2019-09-16 21:29 ` Linus Torvalds
2019-09-16 23:13 ` Andy Lutomirski
2019-09-16 23:26 ` Linus Torvalds
2019-09-17 8:15 ` Borislav Petkov
2019-09-17 10:55 ` David Laight
2019-09-17 20:10 ` Josh Poimboeuf
2019-09-17 20:45 ` Linus Torvalds
2019-09-19 12:55 ` Borislav Petkov
2019-09-19 12:49 ` Borislav Petkov
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=20190914113941.GB28054@zn.tnic \
--to=bp@alien8.de \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/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).