From: Bruce Momjian <bruce@momjian.us>
Date: Fri, 4 Sep 2020 17:27:52 +0000 (-0400)
Subject: C comment:  correct use of 64-"byte" cache line size
X-Git-Tag: REL9_5_24~61
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=226fd0c518bb17e0433422a161b948feef5601d1;p=thirdparty%2Fpostgresql.git

C comment:  correct use of 64-"byte" cache line size

Reported-by: Kelly Min

Discussion: https://postgr.es/m/CAPSbxatOiQO90LYpSC3+svAU9-sHgDfEP4oFhcEUt_X=DqFA9g@mail.gmail.com

Backpatch-through: 9.5
---

diff --git a/src/include/storage/buf_internals.h b/src/include/storage/buf_internals.h
index ecbcf392bc5..a8278f61d09 100644
--- a/src/include/storage/buf_internals.h
+++ b/src/include/storage/buf_internals.h
@@ -166,7 +166,7 @@ typedef struct BufferDesc
  * Note that local buffer descriptors aren't forced to be aligned - as there's
  * no concurrent access to those it's unlikely to be beneficial.
  *
- * We use 64bit as the cache line size here, because that's the most common
+ * We use a 64-byte cache line size here, because that's the most common
  * size. Making it bigger would be a waste of memory. Even if running on a
  * platform with either 32 or 128 byte line sizes, it's good to align to
  * boundaries and avoid false sharing.