From: Alison Schofield <alison.schofield@intel.com>
To: Richard Cheng <icheng@nvidia.com>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jic23@kernel.org>,
Dave Jiang <dave.jiang@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <iweiny@kernel.org>, Li Ming <ming.li@zohomail.com>,
<linux-cxl@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] cxl/test: Add a 2-way 16K root decoder for passthrough testing
Date: Thu, 3 Sep 2026 20:12:36 -0700 [thread overview]
Message-ID: <apo3JK06B3AVHcoG@aschofie-mobl2.lan> (raw)
In-Reply-To: <amxRzTxrPiwhlsx1@MWDK4CY14F>
On Fri, Jul 31, 2026 at 03:44:18PM +0800, Richard Cheng wrote:
> On Fri, Jul 24, 2026 at 06:08:55PM +0800, Alison Schofield wrote:
> > The cxl-test topologies do not provide a configuration where pass-
> > through decoders compute a granularity above the 16K max encodable
> > in hardware. The widest power-of-2 root decoder currently available
> > is 2-way at 4K granularity, so a passthrough decoder below it
> > computes at most 16K.
> >
>
> I think 2-way with 4K granularity computes 8K, not 16K.
> The conclusion does hold, just the number.
Yes and thanks for the review. Fixed up in v4.
-- Alison
next prev parent reply other threads:[~2026-09-04 3:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 1:08 [PATCH v3 0/2] cxl: Allow passthrough decoders with >16K granularity Alison Schofield
2026-07-25 1:08 ` [PATCH v3 1/2] cxl/region: " Alison Schofield
2026-07-25 1:26 ` sashiko-bot
2026-07-25 1:42 ` Alison Schofield
2026-07-31 7:41 ` Richard Cheng
2026-09-04 3:17 ` Alison Schofield
2026-07-25 1:08 ` [PATCH v3 2/2] cxl/test: Add a 2-way 16K root decoder for passthrough testing Alison Schofield
2026-07-31 7:44 ` Richard Cheng
2026-09-04 3:12 ` Alison Schofield [this message]
2026-07-27 23:36 ` [PATCH v3 0/2] cxl: Allow passthrough decoders with >16K granularity Dave Jiang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=apo3JK06B3AVHcoG@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=icheng@nvidia.com \
--cc=iweiny@kernel.org \
--cc=jic23@kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=ming.li@zohomail.com \
--cc=vishal.l.verma@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.