From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: Improving scheduler for KVM Date: Tue, 29 Oct 2013 09:51:43 +0200 Message-ID: <20131029075143.GU15657@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm@vger.kernel.org To: R <19890121wr@gmail.com> Return-path: Received: from mx1.redhat.com ([209.132.183.28]:2683 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751040Ab3J2Hvq (ORCPT ); Tue, 29 Oct 2013 03:51:46 -0400 Content-Disposition: inline In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On Tue, Oct 29, 2013 at 10:20:37AM +0800, R wrote: > Hi, everyone > > I am a graduate student. And now I have some spare time. > I notice that KVM uses kernel scheduler to schedule VCPUs. > But there exists many problem beyond the capability of current > scheduler. (e.g. Lock Waiter Preemption problem) > > And I don't want to reinvent the wheel. So I want to implement a > module which can be used by the scheduler to schedule VCPUs more > efficient. > > Is there any documentation about any problem that I should pay attention to? > Any comment is welcome. > If you are thinking about gang scheduler it was done before, but it will never be accepted upstream. And IIRC pvticketlock result was close if not better than gang scheduling. If you are thinking about something else then implement it in Linux scheduler directly. Linux scheduler is not pluggable, so you cannot change it from a module. -- Gleb.