Differences

This shows you the differences between two versions of the page.

--- nndocs:sandbox [2024/12/29 16:02] – [IQN and NQN] IP numbering doesn't go here naptastic
+++ nndocs:sandbox [2025/07/08 18:41] (current) – naptastic
@@ Line 69: / Line 69: @@
   - 64 bits of GUID
-My top 48 bits are going to be fd00:4e41:5000. Subnet bits should match their Infiniband subnet. Host bits come from the hardware address.
+My top 48 bits are going to be fd20:4e41:5020. Subnet bits should match their Infiniband subnet. Host bits come from the hardware address.
 ====IP Addresses====
@@ Line 81: / Line 81: @@
 ====Networks====
+^ Network ^ IPv4 Range ^ IPv6 Range ^ IB Subnet ^ VLAN ^ VXLAN IP ^ VXLAN ID ^
+| green | 172.20.0/22 | fd20:4e41:5020:ffff::/64. | ffff | | 225.172.20.64 | 64 |
   * 0-3/22: "green": all emo* and eth* devices should get bridged to this network.
@@ Line 148: / Line 151: @@
 ----
+=====Where Data Lives=====
+===Storage===
+  * Production volumes:
+    * janet: 4TB Samsung QVO.
+    * Crucial 120GB SATA SSD boot volume
+      * southpark's boot volume
+    * Samsung 850 512GB NVMe
+      * installed in southpark on the motherboard, I think?
+    * Western Digital Black 2TB NVMe
+      * installed in southpark on the x16 riser card
+      * confusingly mounted at /mnt/sabrent
+    * black: Three 4TB Western Digital enterprise drives in a RAID-5 holding backups; currently cold.
+  * ZFS pool "truck"
+    * Two Sabrent 1TB NVMe drive
+      * installed in southpark on the x16 riser card
+      * Partitioned partly for I don't remember, but it makes sense
+    * four 4TB drives that should really just get recycled
+  * Not installed:
+    * 512GB Crucial SATA SSD (probably for duckling)
+    * 2TB Vulcan Z SATA SSD (probably for shark as a backup)
+===So Where Does Shit Live?===
+  * VM Images:
+    * southpark:/mnt/sabrent/images
+      * exported over NFS-RDMA
+  * TV shows, movies, software, stuff like that: janet
+  * Home directories:
+  * OS volumes:
+I am still struggling with the fact that things really have to boot off local storage. Fibre Channel without a switch isn't worth it and a switch isn't worth it.
+----
 =====Big Idea Dumping Ground=====
+====SoC on a PCI card====
+Mostly this is to enable other projects. It needs at least these features:
+  * reasonable amount of CPU and DRAM
+  * PCIe 3.0 x1 or better
+  * Internal ports:
+    - m.2 slot
+    - Explicitly copy rpi's 40-pin header
+    - LP-DIMM
+  * External ports:
+    - HDMI
+    - gigabit Ethernet
+    - (2) USB 3.1
+The card presents itself to its host as one or more devices. It can pass through its USB host adapter, network adapter, and m.2 slot, and act as a GPU. It supports SR-IOV. You can boot off it. With the right hardware support, it should be able to stay awake while the host powers off or reboots.
 ====PCIe networking====
 These products:
@@ Line 167: / Line 217: @@
 Everything except retimer cards needs an API and UI for managing things.
 ====Better Audio Stack====
 Want to:
@@ Line 178: / Line 229: @@
 ====Better DAW====
 Core concept is a piece of virtual tape that's infinitely long, infinitely wide, and has an infinite number of tape heads that can all be accessed remotely. A recording session is a server you log into, send recorded audio, receive mixed audio, and update a database of what should play when and with what settings.
+====RDMA to a Commodore 64====
+The 6502 can't drive the C64's memory anywhere near full-speed, but the ROM port has a DMA pin, so a DMA-capable cartridge can do impossibly cool things. I'd like to find a good demo playback engine that already exists, and adapt it to play back data being streamed in over a network.
 ====Better Mixer====
 FIXME