Re:Bug 1283585 – Fix Intel's AES-GCM code to not depend on AVX
by protomyth on Sunday October 02, 2016 @10:53PM
(#12625326)
Can someone give a bit of the why on this one? Is there something wrong with AVX or is this a run on other chips thing? I'm at a bit of a loss on the history.
Re:Bug 1283585 – Fix Intel's AES-GCM code to not depend on AVX
by yuhong on Sunday October 02, 2016 @10:54PM
(#12625328)
AVX is normally 256-bit, but it also allows 128-bit instructions with a VEX prefix. Benefits of that include three operands and unaligned access, as well as higher performance when mixed with 256-bit instructions. Of course, you need a AVX-capable CPU and an OS that support AVX XSAVE to be able to use them.
Re:Bug 1283585 – Fix Intel's AES-GCM code to not depend on AVX
by dogma1138 on Monday October 03, 2016 @04:57AM
(#12626101)
AES-NI and AVX were proposed by AMD and Intel at the same time, and were introduced in the same generation of CPUs.
I have a strong feeling that they are interconnected.
Re:Bug 1283585 – Fix Intel's AES-GCM code to not depend on AVX
by pdw on Monday October 03, 2016 @04:17AM
(#12625998)
The x86 architecture has a large number of optional instruction sets. One of these, AES-NI, provides accelerated AES instructions. Another one, AVX, is a collection of general-purpose vector instructions. These were announced at the same time, but it seems like a large number of Intel's low-end CPUs (Celerons & Pentiums) only implement AES-NI.
Firefox's current implementation of the AES-GCM encryption mode uses AVX instructions. The bug report is a submission of a modified implementation that avoids them.
Re:Bug 1283585 – Fix Intel's AES-GCM code to not depend on AVX
by cbhl on Monday October 03, 2016 @12:26AM
(#12625513)
Mozilla set its stuff up before Facebook (2004) even existed, let alone Phabricator.
Bugzilla (1998) predates Phabricator (2010) by about 12 years. It was written in Perl, which was the popular language at the time (similar to PHP around when Facebook happened, or JavaScript now). The first versions of Firefox (2002) predate Phabricator by about 8 years.
Re:Bug 1283585 – Fix Intel's AES-GCM code to not depend on AVX
by mschuster91 on Monday October 03, 2016 @02:17AM
(#12625731)
JIRA is not free, and its main appeals are geared towards enterprise bean counters. Not to mention it is written in Java and as a result has quite heavy requirements on the CPU and RAM.
Upside: it is extremely flexible in ticket workflow design.
(Source: maintaining a 300-user JIRA/Confluence instance at work)
Re:Bug 1283585 – Fix Intel's AES-GCM code to not depend on AVX
by reubenmorais on Sunday October 02, 2016 @11:18PM
(#12625379)
Mozilla does have something like Phabricator, it's called Bugzilla and it's what this thread links to… The only reason you didn't see a pretty diff is because the bug doesn't have a patch attached to it.
Re:Bug 1283585 – Fix Intel's AES-GCM code to not depend on AVX
by dewyatt on Sunday October 02, 2016 @11:27PM
(#12625403)
I know bugzilla has this feature but IIRC it requires much more explicit actions on the part of the user. Like in this case, the user did not upload a patch and mark it as a patch.
Phab, IIRC, kind of forces you to upload a patch and not some random file. Could be remembering wrong, though.
Re:Bug 1283585 – Fix Intel's AES-GCM code to not depend on AVX
by TD-Linux on Monday October 03, 2016 @02:52AM
(#12625805)
Well, Bugzilla uses the same namespace for bugs and patches. The submitter didn't upload patches at all, just asm text files, so from Bugzilla's point of view this is a bug. Not really sure there's anything to "fix" here.
Re:Bug 1283585 – Fix Intel's AES-GCM code to not depend on AVX
by dogma1138 on Monday October 03, 2016 @04:53AM
(#12626086)
AVX is a standardized x86 ISE proposed by both Intel and AMD.
Intel implemented AVX support with Ivy Bridge, AMD has implemented it with Bulldozer these 2 platforms are nearly 6 years old, is there an actual reason to drop support for AVX?
Could someone please provide a context?
Firefox's current implementation of the AES-GCM encryption mode uses AVX instructions. The bug report is a submission of a modified implementation that avoids them.
Bugzilla (1998) predates Phabricator (2010) by about 12 years. It was written in Perl, which was the popular language at the time (similar to PHP around when Facebook happened, or JavaScript now). The first versions of Firefox (2002) predate Phabricator by about 8 years.
Fwiw I was using Bugzilla in 1996. Perhaps it was open sourced in 1998?
I feel it's functional but not great.
Upside: it is extremely flexible in ticket workflow design.
(Source: maintaining a 300-user JIRA/Confluence instance at work)
Phab, IIRC, kind of forces you to upload a patch and not some random file. Could be remembering wrong, though.