On 11 July 2017 at 16:43, Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote: > On Tue, Jul 11, 2017 at 10:26:03PM +0200, Florian Weimer wrote: >> I ran into this unannounced change: >> https://fedoraproject.org/wiki/Changes/Stop_Building_i686_Kernels >> If this is accepted, all x86 hardware on which Fedora can run will >> support SSE2, and we should reflect that in the i686 build flags. >> How likely is it that this proposal is accepted? Ideally, we would know >> this before the mass rebuild so that we can change the compiler flags in >> redhat-rpm-config. > > Currently i686 users are at about 1/6th of x86_64 users, by mirror > checkins. I don't have an easy way of knowing how many of those i686 > checkins are old releases -- I'll need to ask Smooge to make a custom > report -- but I think it's fair to guess that it's significantly tilted > that way. So, taking a SWAG, I'd say maybe 10% of our users would be > impacted. That's pretty big, but on the other hand if the cost is > disproportionate -- and having heard from the kernel people about this > for several years, I think it might be -- it's probably something we > should do anyway. > I will take that as a queue to send a report. For 2017 and F25, the average number of users per day was x86_32 6112.86 x86_64 101186 percentage x86_32 5.44475 percentage x86_64 93.9021 Now this doesn't say whether that hardware could run x86_64 kernels with an x86_32 userspace. It just says that on average of ~6% of users are using x86_32 currently. For some images https://smooge.fedorapeople.org/stats-f25/ [The raw numbers are not as useful as the ratios due to the way numbers of users get their internet these days. A single user in India and China will show up as multiple ip addresses at the 'same time' as their public ip address is rolled around via NAT over NAT hardware. What this means is that while the raw numbers show a growth in x86_32 users in May->July those all came from India with an equal ratio growth in x86_64 users. ] -- Stephen J Smoogen. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx