[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241031002422.cu53abpaimetzrdx@offworld>
Date: Wed, 30 Oct 2024 17:24:22 -0700
From: Davidlohr Bueso <dave@...olabs.net>
To: ira.weiny@...el.com
Cc: Dave Jiang <dave.jiang@...el.com>, Fan Ni <fan.ni@...sung.com>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
Navneet Singh <navneet.singh@...el.com>,
Jonathan Corbet <corbet@....net>,
Andrew Morton <akpm@...ux-foundation.org>,
Dan Williams <dan.j.williams@...el.com>,
Alison Schofield <alison.schofield@...el.com>,
Vishal Verma <vishal.l.verma@...el.com>, linux-cxl@...r.kernel.org,
linux-doc@...r.kernel.org, nvdimm@...ts.linux.dev,
linux-kernel@...r.kernel.org, Kees Cook <kees@...nel.org>,
"Gustavo A. R. Silva" <gustavoars@...nel.org>,
linux-hardening@...r.kernel.org
Subject: Re: [PATCH v5 08/27] cxl/mem: Read dynamic capacity configuration
from the device
On Tue, 29 Oct 2024, ira.weiny@...el.com wrote:
>Linux has no use for the trailing fields of the Get Dynamic Capacity
>Configuration Output Payload (Total number of supported extents, number
>of available extents, total number of supported tags, and number of
>available tags). Avoid defining those fields to use the more useful
>dynamic C array.
More of a general question, if anyone knows: why does the spec define
the fields in that order, and not put the region config structure(s)
at the end, as with all other cmds, afaik.
Powered by blists - more mailing lists