From: Dan Williams <dan.j.williams@intel.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Vikram Sethi <vsethi@nvidia.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"Natu, Mahesh" <mahesh.natu@intel.com>,
"Rudoff, Andy" <andy.rudoff@intel.com>,
Jeff Smith <JSMITH@nvidia.com>,
Mark Hairgrove <mhairgrove@nvidia.com>,
"jglisse@redhat.com" <jglisse@redhat.com>,
David Hildenbrand <david@redhat.com>,
Linux MM <linux-mm@kvack.org>,
Linux ACPI <linux-acpi@vger.kernel.org>
Subject: Re: Onlining CXL Type2 device coherent memory
Date: Fri, 30 Oct 2020 16:38:06 -0700 [thread overview]
Message-ID: <CAPcyv4iNeTGrLLN6XLOc+c9CRUODfw9bi0GpjpJuYywniP6dXg@mail.gmail.com> (raw)
In-Reply-To: <20201030205956.GO27442@casper.infradead.org>
On Fri, Oct 30, 2020 at 2:00 PM Matthew Wilcox <willy@infradead.org> wrote:
>
> On Fri, Oct 30, 2020 at 01:37:18PM -0700, Dan Williams wrote:
> > On Wed, Oct 28, 2020 at 4:06 PM Vikram Sethi <vsethi@nvidia.com> wrote:
[..]
>
> i don't know what you're talking about but you must both work for
> hardware manufacturers!
If only there was some software project that could comprehend these
details and synthesize an interface for applications to use. Even
better if this project had mailing lists with experts that could parse
the acronym soup into code patches.
next prev parent reply other threads:[~2020-10-30 23:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 23:05 Onlining CXL Type2 device coherent memory Vikram Sethi
2020-10-29 14:50 ` Ben Widawsky
2020-10-30 20:37 ` Dan Williams
2020-10-30 20:59 ` Matthew Wilcox
2020-10-30 23:38 ` Dan Williams [this message]
2020-10-30 22:39 ` Vikram Sethi
2020-11-02 17:47 ` Dan Williams
2020-10-31 10:21 ` David Hildenbrand
2020-10-31 16:51 ` Dan Williams
2020-11-02 9:51 ` David Hildenbrand
2020-11-02 16:17 ` Vikram Sethi
2020-11-02 17:53 ` David Hildenbrand
2020-11-02 18:03 ` Dan Williams
2020-11-02 19:25 ` Vikram Sethi
2020-11-02 19:45 ` Dan Williams
2020-11-03 3:56 ` Alistair Popple
2020-11-02 18:34 ` Jonathan Cameron
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=CAPcyv4iNeTGrLLN6XLOc+c9CRUODfw9bi0GpjpJuYywniP6dXg@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=JSMITH@nvidia.com \
--cc=andy.rudoff@intel.com \
--cc=david@redhat.com \
--cc=jglisse@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mahesh.natu@intel.com \
--cc=mhairgrove@nvidia.com \
--cc=vsethi@nvidia.com \
--cc=willy@infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).