Commitdc6070b

committed

Update PG_CACHE_LINE_SIZE description.

PG_CACHE_LINE_SIZE was originally only used in xlog.c, but this hasn'tbeen true for a very long time and is now wildly used, so modify itsdescription to not mention any explicit source code file.Author: Julien RouhaudDiscussion:https://www.postgresql.org/message-id/20230701074936.p3qcssl4t7murt2q@jrouhaud

1 parent9945750 commitdc6070bCopy full SHA for dc6070b

File tree

-7

lines changed

-7

lines changed

Lines changed: 7 additions & 7 deletions

Original file line number	Diff line number	Diff line change
`@@ -217,13 +217,13 @@`
`217`	`217`	`#defineDEFAULT_EVENT_SOURCE "PostgreSQL"`
`218`	`218`
`219`	`219`	`/*`
`220`		`- * Assumed cache line size. This doesn't affect correctness, but can be used`
`221`		`- * for low-level optimizations.Currently, this is used to padsome data`
`222`		`- * structures in xlog.c, to ensure that highly-contended fields are on`
`223`		`- *different cachelines. Too small a value can hurt performance due to false`
`224`		`- *sharing, whilethe only downside of too large a value is a few bytes of`
`225`		`- *wasted memory.The default is 128, which should be large enough for all`
`226`		`- *supportedplatforms.`
	`220`	`+ * Assumed cache line size.This doesn't affect correctness, but can be used`
	`221`	`+ * for low-level optimizations. This ismostlyused to padvarious data`
	`222`	`+ * structures, to ensure that highly-contended fields are on different cache`
	`223`	`+ * lines.Too small a value can hurt performance due to false sharing, while`
	`224`	`+ * the only downside of too large a value is a few bytes of wasted memory.`
	`225`	`+ * The default is 128, which should be large enough for all supported`
	`226`	`+ * platforms.`
`227`	`227`	`*/`
`228`	`228`	`#definePG_CACHE_LINE_SIZE128`
`229`	`229`

Comments

(0)