Scroll to bottom (removing the v2-specific patch text and review as it's
not relevant to my v1 commentary):
On 1/16/20 7:46 AM, Vladimir Homutov wrote:
[snip]
On Thu, Jan 16, 2020 at 07:39:07AM -0800, Joe Konno wrote:
[snip]
v1 of that patch used CPUID to retrieve the cache line
Scroll to bottom:
On 1/16/20 6:43 AM, Vladimir Homutov wrote:
On Fri, Jan 03, 2020 at 02:39:29PM -0800, Joe Konno wrote:
# HG changeset patch
# User Joe Konno
# Date 1578075036 28800
# Fri Jan 03 10:10:36 2020 -0800
# Node ID b66ee34cea2f539bb8ce4986d6bd332f75ee06b6
# Parent
# HG changeset patch
# User Joe Konno
# Date 1578075036 28800
# Fri Jan 03 10:10:36 2020 -0800
# Node ID b66ee34cea2f539bb8ce4986d6bd332f75ee06b6
# Parent f1720934c45be1c6469841a55d1f31fe9a630c85
remove ngx_cpuinfo, use sysconf or define
Function ngx_cpuinfo() is used to (sub-optimally
# HG changeset patch
# User Joe Konno
# Date 1577125916 28800
# Mon Dec 23 10:31:56 2019 -0800
# Node ID e5427bbc1db2b49424025400783c80f5c75be5fe
# Parent f609c0ac2972f6f451ffe2d17e268ec80802ec94
ngx_cpuinfo: x86: CPUID to set ngx_cacheline_size
Previously, vendor string information was
On 11/19/19 3:15 PM, Sergey A. Osokin wrote:
> Hi Joe,
>
> hope you're doing well.
>
> I'm supporting nginx for FreeBSD ports tree for years and we usually don't
> use '--with-cpu-opt' flag for the port/package build. Also, this is the
> general
> recommendation described on FreeBSD Porters Han
Hey all,
I'm requesting comment/input on how nginx would like to do architecture
detection at build time as well as at run time. This is for the purposes
of optimizing nginx for specific hardware (see my e-mail address for
what specific hardware I hope to optimize for). ^_^
For build time, I see
