d/numam-spdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
numam-spdk/lib/vhost/test_plan.md
Tomasz Zawadzki c0e6ecaa0b test/vhost: add vhost with lvol backends test 
Script for testing vhost using lvols as backends for
virtual machines. Option for using nested lvol stores and
nested lvol bdevs also provided.

Change-Id: Iad8a196c97f292881a8b424b4433ec281f12aec6
Signed-off-by: Lukasz <lukaszx.galka@intel.com>
Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Signed-off-by: Karol Latecki <karol.latecki@intel.com>
Reviewed-on: https://review.gerrithub.io/365798
Reviewed-by: Maciej Szwed <maciej.szwed@intel.com>
Tested-by: SPDK Automated Test System <sys_sgsw@intel.com>
Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com>
2017-09-20 12:53:28 -04:00

4.4 KiB
Raw Blame History

SPDK vhost Test Plan

Current Tests

Integrity tests

vhost self test

  • compiles SPDK and Qemu
  • launches SPDK Vhost
  • starts VM with 1 NVMe device attached to it
  • issues controller "reset" command using sg3_utils on guest system
  • performs data integrity check using dd to write and read data from the device
  • runs on 3 host systems (Ubuntu 16.04, Centos 7.3 and Fedora 25) and 1 guest system (Ubuntu 16.04)
  • runs against vhost scsi and vhost blk

FIO Integrity tests

  • NVMe device is split into 4 LUNs, each is attached to separate vhost controller
  • FIO uses job configuration with randwrite mode to verify if random pattern was written to and read from correctly on each LUN
  • runs on Fedora 25 and Ubuntu 16.04 guest systems
  • runs against vhost scsi and vhost blk

Lvol tests

  • starts vhost with at least 1 NVMe device
  • starts 1 VM or multiple VMs
  • lvol store is constructed on each NVMe device
  • on each lvol store 1 lvol bdev will be constructed for each running VM
  • Logical volume block device is used as backend instead of using NVMe device backed directly
  • after set up, data integrity check will be performed by FIO randwrite operation with verify flag enabled
  • optionally nested lvols can be tested with use of appropriate flag; On each base lvol store additional lvol bdev will be created which will serve as a base for nested lvol stores. On each of the nested lvol stores there will be 1 lvol bdev created for each VM running. Nested lvol bdevs will be used along with base lvol bdevs for data integrity check.
  • runs against vhost scsi and vhost blk

Filesystem integrity

  • runs SPDK with 1 VM with 1 NVMe device attached.
  • creates a partition table and filesystem on passed device, and mounts it
  • runs Linux kernel source compilation
  • Tested file systems: ext2, ext3, ext4, brtfs, ntfs, fat
  • runs against vhost scsi and vhost blk

Windows HCK SCSI Compliance Test 2.0.

  • Runs SPDK with 1 VM with Windows Server 2012 R2 operating system
  • 4 devices are passed into the VM: NVMe, Split NVMe, Malloc and Split Malloc
  • On each device Windows HCK SCSI Compliance Test 2.0 is run

MultiOS test

  • start 3 VMs with guest systems: Ubuntu 16.04, Fedora 25 and Windows Server 2012 R2
  • 3 physical NVMe devices are split into 9 LUNs
  • each guest uses 3 LUNs from 3 different physical NVMe devices
  • Linux guests run FIO integrity jobs to verify read/write operations, while Windows HCK SCSI Compliance Test 2.0 is running on Windows guest

vhost hot-remove tests

  • removing NVMe device (unbind from driver) which is already claimed by controller in vhost
  • hotremove tests performed with and without I/O traffic to device
  • I/O traffic, if present in test, has verification enabled
  • checks that vhost and/or VMs do not crash
  • checks that other devices are unaffected by hot-remove of a NVMe device
  • performed against vhost blk and vhost scsi

vhost scsi hot-attach and hot-detach tests

  • adding and removing devices via RPC to a controller which is already in use by a VM
  • I/O traffic generated with FIO read/write operations, verification enabled
  • checks that vhost and/or VMs do not crash
  • checks that other devices in the same controller are unaffected by hot-attach and hot-detach operations

Performance tests

Tests verifying the performance and efficiency of the module.

FIO Performance 6 NVMes

  • SPDK is run on 2 CPU cores

  • Run with vhost scsi

  • 6 VMs are run with 2 cores, 1 controller (2 queues), 1 Split NVMe LUN each

  • FIO configurations runs are 15 minute job combinations of:

    • IO depth: 1, 8, 128
    • Blocksize: 4k
    • RW modes: read, randread, write, randwrite, rw, randrw

    Write modes are additionally run with 10 minute ramp-up time to allow better measurements. Randwrite mode uses longer ramp-up preconditioning of 90 minutes per run.

Full Performance Suite

On-demand performance tests allowing to run test jobs which can be combinations of:

  • SPDK cores: 1-3 CPU cores,
  • VM cores: 1-5 CPU cores per VM,
  • VM count: 1-12,
  • vhost controller queues: single, multi
  • FIO IO depth: 1, 2, 4, 8, 32, 64, 128
  • FIO Blocksize: 4k
  • FIO RW modes: read, randread, write, randwrite, rw, randrw
  • each test job takes from 30 to 120 minutes

Future tests and improvements

Performance tests

  • Establish a baseline for acceptance level of FIO Performance 6 NVMe test results

Stress tests

  • Add stability and stress tests (long duration tests, long looped start/stop tests, etc.) to test pool