Mercurial > hg > nginx
view src/os/unix/ngx_setaffinity.h @ 7669:52b34c3f89b4
Too large st_blocks values are now ignored (ticket #157).
With XFS, using "allocsize=64m" mount option results in large preallocation
being reported in the st_blocks as returned by fstat() till the file is
closed. This in turn results in incorrect cache size calculations and
wrong clearing based on max_size.
To avoid too aggressive cache clearing on such volumes, st_blocks values
which result in sizes larger than st_size and eight blocks (an arbitrary
limit) are no longer trusted, and we use st_size instead.
The ngx_de_fs_size() counterpart is intentionally not modified, as
it is used on closed files and hence not affected by this problem.
author | Maxim Dounin <mdounin@mdounin.ru> |
---|---|
date | Mon, 22 Jun 2020 18:02:59 +0300 |
parents | 7296b38f6416 |
children |
line wrap: on
line source
/* * Copyright (C) Nginx, Inc. */ #ifndef _NGX_SETAFFINITY_H_INCLUDED_ #define _NGX_SETAFFINITY_H_INCLUDED_ #if (NGX_HAVE_SCHED_SETAFFINITY || NGX_HAVE_CPUSET_SETAFFINITY) #define NGX_HAVE_CPU_AFFINITY 1 #if (NGX_HAVE_SCHED_SETAFFINITY) typedef cpu_set_t ngx_cpuset_t; #elif (NGX_HAVE_CPUSET_SETAFFINITY) #include <sys/cpuset.h> typedef cpuset_t ngx_cpuset_t; #endif void ngx_setaffinity(ngx_cpuset_t *cpu_affinity, ngx_log_t *log); #else #define ngx_setaffinity(cpu_affinity, log) typedef uint64_t ngx_cpuset_t; #endif #endif /* _NGX_SETAFFINITY_H_INCLUDED_ */