Content-Type: multipart/mixed; boundary="===============8811623082514777800==" MIME-Version: 1.0 From: Klaus Jensen Subject: [SPDK] Re: NVMe devices with CMB Date: Mon, 08 Nov 2021 09:29:41 +0100 Message-ID: In-Reply-To: 20211104223957.2830.14913@ml01.vlan13.01.org List-ID: To: spdk@lists.01.org --===============8811623082514777800== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Nov 4 22:39, Kit Chow wrote: > Hi Benjamin, > = > I found the following qemu nvme blog - http://blog.frankenmichl.de/2018/0= 2/13/add-nvme-device-to-vm/ > = > Following the instructions, I get the NVMe device listed below with a bar= 4 size of 4K. Is this the CMB and is it large enough for small p2p copies? > = Hi Kit, You need to specifically enable the CMB with the `cmb_size_mb` parameters (argument in MBs). -device "nvme,id=3Dnvme0,serial=3Ddeadbeef,cmb_size_mb=3D64" Looks like you are using a pretty old version of QEMU. In current versions the CMB is exclusively using BAR 4 - I think what you are seeing is an older version where the MSI-X tables were in BAR4. --===============8811623082514777800== Content-Type: application/pgp-signature MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlRRXpCQUVCQ0FBZEZpRUVVaWd6cW5YaTNP YWlSMmJBVGVHdk1XMVBEZWtGQW1HSTMvUUFDZ2tRVGVHdk1XMVAKRGVuNGxnZitQcjcyTThGRWlm TFJBd0pEN1ZtZG5UYUJsUFB1M0tOZ2c5NE1TeHN5OEJEUHFYdHBVZWh1b2pJOQpJdjNpQ3piR0Q5 WWFqVTJGUlB2SS9NcWNkQUZUSk84YkdPL2NJa2hTdmZLamhOc0tGR25MTStqaVNnZjQ1azdwCjVv YmV3bDFDeUNra3NJYW4zMlJ5aUlFNUZ6TXQyVXZCS1Z0cTlmMUZtUXp6WVdXMnBWaUdNRWxLbTUz M1ZtNnoKNTMvbDliSm1JQlFJKzg3T1JGSmR6VCtRcEpvVTVlQWQ1VGswQmswYlJYYU56MFhnWFA5 emVtNzFCTkxwNXQzQQpPc3Z3MEtLSUdMRERmT2FTdUwxcE1KQ1NLeXNJSkV0WklKaUdCK1NNUDBN MVkwUnpCMGZSZWlLZStUdG00b1ZsCkFYa3YrbXpXL2ViV0RRdXhvaWRwdTI2bDh3TXpldz09Cj1u Rk41Ci0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQo= --===============8811623082514777800==--