Path: ...!weretis.net!feeder9.news.weretis.net!i2pn.org!i2pn2.org!.POSTED!not-for-mail From: mitchalsup@aol.com (MitchAlsup1) Newsgroups: comp.arch Subject: Re: PCIe MSI-X interrupts Date: Sat, 22 Jun 2024 22:14:17 +0000 Organization: Rocksolid Light Message-ID: <4b671980d874826c331b1bd930b50d3b@www.novabbs.org> References: <0faeb2831a76d32cd6fb8cff7b546807@www.novabbs.org> <6caaf9cb208191a70900c68ac4ce0562@www.novabbs.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: i2pn2.org; logging-data="854415"; mail-complaints-to="usenet@i2pn2.org"; posting-account="65wTazMNTleAJDh/pRqmKE7ADni/0wesT78+pyiDW8A"; User-Agent: Rocksolid Light X-Spam-Checker-Version: SpamAssassin 4.0.0 X-Rslight-Posting-User: ac58ceb75ea22753186dae54d967fed894c3dce8 X-Rslight-Site: $2y$10$ht7B5gOrL.vL7qzpcNdACu/gt3IXHyZz2VEku5urvRKryvKgir9rS Bytes: 2048 Lines: 28 Scott Lurndal wrote: Snipping a whole lot of information I had a basic knowledge of but were not part of original tree of question being ask. But thanks for the details--they help a lot. >>> You basically need a root per device to accommodate SRIOV >>> devices (like enterprise grade network adapters, high-end >>> NVMe devices, etc). >> >>As noted above: I knew more bits than B:D,F were needed, >>but not which and where. Or even the name of what I am searching Google for..... ECAM for example. > And if a single SR-IOV device >>consumes a whole B:D,F space sobeit. ECAM alignment >>identifies those bits and the routings. > Ah, I should have read this one backwards :-) You know, sometimes when reading and writing these posts What I need to write changes with my knowledge base and some of the earlier writings become stale wrt what I now grasp. My thanks again.