<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 18, 2016 at 11:35 AM, Nitin Varyani <span dir="ltr"><<a href="mailto:varyani.nitin1@gmail.com" target="_blank">varyani.nitin1@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">@ Greg: Since I am very new to the field, with the huge task in hand<br>
and a short time span of 3 months given for this project, I am looking<br>
for specific directions from the linux experts to work on. As far as<br>
efforts are concerned, I am taking out hours together to research into<br>
this area. I do not mind telling this to my professor. Still, I am<br>
always looking for improvement. I will try to put more endeavor and<br>
seek as less help as possible. I hope you will not mind my reply.<br>
Thanks.<br>
<div class="HOEnZb"><div class="h5"><br>
On Wed, Feb 17, 2016 at 9:02 PM, Greg KH <<a href="mailto:greg@kroah.com">greg@kroah.com</a>> wrote:<br>
> On Wed, Feb 17, 2016 at 04:05:17PM +0530, Nitin Varyani wrote:<br>
>> Rather than trying to go blind folded in getting practical experience<br>
>> of linux programming, I want to gain experience only in relation to my<br>
>> task of creating a distributed process scheduler. What all things<br>
>> should I try to work with to understand the kernel CFS scheduler well?<br>
>> Please provide sufficient literature for the practical work.<br>
>> Also what is the best place to learn about implementing linux containers?<br>
><br>
> Why are you asking other people to do your research work for you?<br>
> That's pretty rude, does your professor know this is what you are doing?<br>
><br>
> greg k-h<br>
<br></div></div></blockquote></div><br><br></div><div class="gmail_extra">Dear Nitin<br><br></div><div class="gmail_extra">Again, please don't top post :) That's considered rude too, at least here :)<br><br></div><div class="gmail_extra">I can't speak on behalf of Greg, but I guess the basic idea of why people gather in this mailing list is to share ideas and discuss, but not giving very specific guidance. If that's the goal, this list would be named "kernel mentoring", don't you agree? :)<br><br></div><div class="gmail_extra">So, if we follow this "discussion area" rule, I can give you ideas:<br></div><div class="gmail_extra">- maybe your scope of work is too wide. Try to be more specific. 3 months time span is very short compared to what you're going to do (IIUC). As other already pointed, maybe you can piggy back on Erlang project and enhance their work instead?<br><br></div><div class="gmail_extra">- do you have solid background of kernel programming, especially related to scheduler? if not, try to get a grasp quickly using code navigator e.g cscope or <a href="http://lxr.linux.no">lxr.linux.no</a> and play around with the code first. It might give direct experience on how code works and at the same time how kernel build mechanism work<br><br></div><div class="gmail_extra">Hope it helps....<br clear="all"></div><div class="gmail_extra"><br>-- <br><div class="gmail_signature">regards,<br><br>Mulyadi Santosa<br>Freelance Linux trainer and consultant<br><br>blog: <a href="http://the-hydra.blogspot.com" target="_blank">the-hydra.blogspot.com</a><br>training: <a href="http://mulyaditraining.blogspot.com" target="_blank">mulyaditraining.blogspot.com</a></div>
</div></div>