From: Dario Faggioli <raistlin@linux.it>
To: Rajendra Bele <belerajendra753@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Xen Virtualization Algorithms
Date: Fri, 20 Jul 2012 09:51:51 +0200 [thread overview]
Message-ID: <1342770711.19530.240.camel@Solace> (raw)
In-Reply-To: <CAJRmKy8Zv=CZ7Y1iXSQNBAD-bGe5q_qPkD+pc_SH_RCCbmd7Hw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 966 bytes --]
On Fri, 2012-07-20 at 12:41 +0530, Rajendra Bele wrote:
> Dear Friends;
>
Hi,
> I wish to enhance some Xen Algorithms, most probably CPU Scheduling;
>
Wow, cool.
>
> Can any one guide me to identify specific code for these algorithms
> from Xen Source code;
>
I'd recommend running something like the below from the root of a Xen
source tree:
find xen/ -iname sched*
It might not be perfect, but should be enough as a starting point.
>
> Also I wanted to know which programming has used in Xen Source code
> development.
>
> whether it is python or C or something else.
>
The above command _should_ pretty much answer this question too. :-D
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2012-07-20 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 7:11 Xen Virtualization Algorithms Rajendra Bele
2012-07-20 7:21 ` Ian Campbell
2012-07-20 7:51 ` Dario Faggioli [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=1342770711.19530.240.camel@Solace \
--to=raistlin@linux.it \
--cc=belerajendra753@gmail.com \
--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).