From: Dario Faggioli <dario.faggioli@citrix.com>
To: Abhinav Gupta <abhinavgupta440@gmail.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: Interested in taking up a project
Date: Wed, 1 Jul 2015 15:11:53 +0200 [thread overview]
Message-ID: <1435756313.25170.350.camel@citrix.com> (raw)
In-Reply-To: <CALc02L5TdRm=jnszuLWzUAL55hNq2E+W0aQJiRVtY5xkJmjtiQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1913 bytes --]
On Wed, 2015-06-24 at 09:56 +0000, Abhinav Gupta wrote:
> Thanks for the help and support guys. I'll need some time to get a
> proper understanding of how it is incorporated in Linux kernel and
> what all interfaces are built on top of it.
>
Sure! Of course, that was just a suggestion, and we are mostly
interested in having this in Xen, not about how the Linux implementation
works.
Actually, I do believe that, if the thing is popular on Linux, and if
there are user-level (or whatever-level) tools that interact with it, a
common (or at least a compatible and easy to adapt) interface would be a
great plus (for us!), but really, don't go too much deep with that.
What I really meant was that, if it were me doing this, I'd at least
have a look, with the aim of figuring out how actually popular, useful
and used this is in the Linux world. If it's used a lot, then we can see
about being compatible with it. If it's just some forgotten piece of
code inside the kernel, then we can implement our own variant of it,
without caring of Linux's interface and user space tools!
> Once I'm comfortable with that and xen's credit_scheduler, for
> starting, I'll come up with a design doc and share with you all.
>
Sure, that would be great.
> I'll keep reporting the progress of the work and ask related doubts in
> this thread.
>
Or, feel free to use this thread for updates, but open new ones for
specific questions or issues.
As soon as you read, understand and follow:
http://wiki.xenproject.org/wiki/Asking_Developer_Questions
Go ahead and ask whatever you need help and advise with! :-)
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.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: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-07-01 13:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 7:02 Interested in taking up a project Abhinav Gupta
2015-06-19 9:11 ` Wei Liu
[not found] ` <CALc02L7+MtwBOg4iFn2uri0MGKu_XSrdxA-LyzQ-59LuEsJ-RQ@mail.gmail.com>
2015-06-19 10:56 ` Wei Liu
2015-06-21 6:37 ` Abhinav Gupta
2015-06-22 8:37 ` Dario Faggioli
2015-06-22 9:45 ` George Dunlap
2015-06-24 9:56 ` Abhinav Gupta
2015-07-01 13:11 ` Dario Faggioli [this message]
2015-07-10 20:33 ` Abhinav Gupta
2015-07-13 9:45 ` Dario Faggioli
2015-07-25 12:34 ` Abhinav Gupta
2015-07-27 14:20 ` Dario Faggioli
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=1435756313.25170.350.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=abhinavgupta440@gmail.com \
--cc=george.dunlap@eu.citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.