linux-kernel - [RFC] kvm: export host NUMA info to guest's scheduler

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1337754751-9018-1-git-send-email-kernelfans@gmail.com>
Date:	Wed, 23 May 2012 14:32:27 +0800
From:	Liu Ping Fan <kernelfans@...il.com>
To:	kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
	qemu-devel@...gnu.org
Cc:	Ingo Molnar <mingo@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Avi Kivity <avi@...hat.com>,
	Anthony Liguori <anthony@...emonkey.ws>
Subject: [RFC] kvm: export host NUMA info to guest's scheduler

Currently, the guest can not know the NUMA info of the vcpu, which will
result in performance drawback. For example:
  Supposing vcpu-a on nodeA, vcpu-b on nodeB, when load balance,
the tasks' pull and push between these vcpus will cost more. But
unfortunately, currently, the guest is just blind to this.

So here is the idea to solve it.
  Export host numa info through guest's sched domain to its scheduler.
  So the guest's lb will consider the cost.

These patches include:
For guest:
  0001-sched-add-virt-sched-domain-for-the-guest.patch
  0002-sched-add-virt-domain-device-s-driver.patch
For host:
  0001-kvm-collect-vcpus-numa-info-for-guest-s-scheduler.patch  
  0001-Qemu-add-virt-sched-domain-device.patch

Please give some comments and suggestion.

Thanks and regards,
pingfan

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/