[DTrace-devel] [PATCH 5/5] Use array-of-maps as storage for aggregations

[Eugene Loh]

What's puzzling is that we're changing from a fixed area on each CPU to... a fixed area on each CPU.  Anyhow, it just seemed to me that that last sentence didn't add anything that wasn't already said.

________________________________
From: Kris Van Hees <kris.van.hees at oracle.com>
Sent: Monday, August 22, 2022 5:21 PM
To: Eugene Loh <eugene.loh at oracle.com>

On Mon, Aug 22, 2022 at 03:28:08PM -0400, Eugene Loh wrote:
>
> *)  The last sentence of the commit message is, let's say, "puzzling."  Just
> drop it?

What is puzzling about it?

> From: Kris Van Hees via DTrace-devel <dtrace-devel at oss.oracle.com>
> Sent: Friday, August 19, 2022 10:26 AM
>
> In preparation for indexed aggregations and the clear() and trunc()
> operations, the storage for aggregations is moving from a per-CPU
> array map to an array of maps, indexed by CPU id.  This gives each
> CPU it's own storage to store aggregation data in.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://oss.oracle.com/pipermail/dtrace-devel/attachments/20220823/e7e93a44/attachment.html>