All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viacheslav Dubeyko <slava@dubeyko.com>
To: Jonathan.Cameron@huawei.com
Cc: linux-cxl@vger.kernel.org, a.manzanares@samsung.com,
	viacheslav.dubeyko@bytedance.com,
	Viacheslav Dubeyko <slava@dubeyko.com>
Subject: CXL Fabric Manager (FM) architecture diagrams
Date: Mon,  6 Mar 2023 10:59:13 -0800	[thread overview]
Message-ID: <20230306185913.1060918-1-slava@dubeyko.com> (raw)

Hi Jonathan,

You can find diagram online now:

(1) Diagram 1: single host with Fabric Manager (FM)
https://github.com/computexpresslink/cxl-fm-architecture/blob/main/diagram1-cxl-fm-single-host-with-fm.pdf

(2) Diagram 2: single host with orchestrator
https://github.com/computexpresslink/cxl-fm-architecture/blob/main/diagram2-cxl-fm-single-host-with-orhestrator.pdf

(3) Diagram3: Multi-headed device
https://github.com/computexpresslink/cxl-fm-architecture/blob/main/diagram3-cxl-fm-multi-headed-device.pdf

(4) Diagram 4: Multi-headed device + Orchestrator
https://github.com/computexpresslink/cxl-fm-architecture/blob/main/diagram4-cxl-fm-multi-headed-device-orchestrator.pdf

(5) Diagram5: Multiple hosts with Fabric Manager (FM)
https://github.com/computexpresslink/cxl-fm-architecture/blob/main/diagram5-cxl-fm-multiple-hosts-with-fm.pdf

(6) Diagram 6: Multiple hosts with orhestrator
https://github.com/computexpresslink/cxl-fm-architecture/blob/main/diagram6-cxl-fm-multiple-hosts-with-orhestrator.pdf

(7) Diagram 7: Distributed Fabric Manager (FM)
https://github.com/computexpresslink/cxl-fm-architecture/blob/main/diagram7-cxl-fm-distributed-fm.pdf

(8) Diagram 8: Layered Fabric Manager (FM) and separate orchestrator
https://github.com/computexpresslink/cxl-fm-architecture/blob/main/diagram8-cxl-fm-layered-fm-and-separate-orchestrator.pdf

(9) Diagram 9: BMC based layered Fabric Manager (FM)
https://github.com/computexpresslink/cxl-fm-architecture/blob/main/diagram9-cxl-fm-bmc-based-layered-fm.pdf

So, have I missed something?
Should we correct something on diagrams?
Does it look good?

Thanks,
Slava.

             reply	other threads:[~2023-03-06 19:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06 18:59 Viacheslav Dubeyko [this message]
2023-03-07 17:21 ` CXL Fabric Manager (FM) architecture diagrams Jonathan Cameron
2023-03-09 22:28   ` [External] " Viacheslav A.Dubeyko
     [not found]     ` <20230310120126.000057b9@Huawei.com>
2023-03-16 20:43       ` Viacheslav A.Dubeyko
     [not found]         ` <20230406204227.GA5971@bgt-140510-bm01>
2023-04-07 18:18           ` Viacheslav A.Dubeyko
     [not found]             ` <90aea04c-dab2-4b7e-bfc6-09a1240793a9@nmtadam.samsung>
2023-04-07 23:24               ` Viacheslav A.Dubeyko

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=20230306185913.1060918-1-slava@dubeyko.com \
    --to=slava@dubeyko.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=a.manzanares@samsung.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=viacheslav.dubeyko@bytedance.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.