From: George Dunlap <dunlapg@gmail.com>
To: prakash hegade <kickputts@yahoo.co.in>
Cc: xen-devel@lists.xensource.com
Subject: Re: Query regarding schedulers in Xen
Date: Tue, 30 Mar 2010 10:39:57 +0100 [thread overview]
Message-ID: <de76405a1003300239ib359af9g4fb1efa0c53a02e8@mail.gmail.com> (raw)
In-Reply-To: <819907.1698.qm@web8705.mail.in.yahoo.com>
Try something like this:
$ pwd
/path/to/xen-unstable.hg
$ find . -name "*sched*"
-George
On Thu, Mar 4, 2010 at 7:03 PM, prakash hegade <kickputts@yahoo.co.in> wrote:
> Hello,
>
> We are in project to modify the scheduler in Xen.
> We are working on openSUSE 11.2
>
> We are unable to find the documentation or where exactly the sedf / Credit
> scheduler codes are written.
>
> Kindly help us.
>
> Thanking,
> Team Members.
>
> ________________________________
> Your Mail works best with the New Yahoo Optimized IE8. Get it NOW!.
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
prev parent reply other threads:[~2010-03-30 9:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 18:03 Query regarding schedulers in Xen prakash hegade
2010-03-30 9:39 ` George Dunlap [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=de76405a1003300239ib359af9g4fb1efa0c53a02e8@mail.gmail.com \
--to=dunlapg@gmail.com \
--cc=kickputts@yahoo.co.in \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).