linux-kernel - Re: [PATCH] x86-64: fix memset() to support sizes of 4Gb and above

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120106190154.GA4164@elte.hu>
Date:	Fri, 6 Jan 2012 20:01:54 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Jan Beulich <JBeulich@...e.com>
Cc:	tglx@...utronix.de, Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, hpa@...or.com
Subject: Re: [PATCH] x86-64: fix memset() to support sizes of 4Gb and above


* Jan Beulich <JBeulich@...e.com> wrote:

> > Would be nice to add support for arch/x86/lib/memset_64.S as 
> > well, and look at the before/after performance of it. In 
> > userspace we can do a lot more accurate measurements of this 
> > kind:
> 
> I'll see whether I can get this done, but I admit that I'm 
> entirely unfamiliar with this tool and its infrastructure. 
> [...]

Just check what it does for memcpy and duplicate it.

> [...] I hope doing this is not going to be a requirement for 
> acceptance of the patch.

No, but it would certainly help us make sure there's no 
performance side effect.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/