From: Sachin Agarwalla <sachin.agarwalla@cse.iitkgp.ernet.in>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: need help on development of linux kernel
Date: Tue, 4 Sep 2012 14:40:08 +0530 (IST) [thread overview]
Message-ID: <1283617617.10114.1346749808002.JavaMail.root@mailstore2.iitkgp.ac.in> (raw)
In-Reply-To: <5045A6C9.8000101@gmail.com>
Dear Sir/Madam,
Thank you for your support.I want to know is the linux kernel cpu scheduling part optimized for scalable multi core architecture.If not then what are the scope if improvements?Can you help me?
thanking you,
waiting for your reply,
yours faithfully,
sachinagarwalla
----- Original Message -----
From: "Cong Wang" <xiyou.wangcong@gmail.com>
To: "Sachin Agarwalla" <sachin.agarwalla@cse.iitkgp.ernet.in>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>
Sent: Tuesday, September 4, 2012 12:29:21 PM
Subject: Re: need help on development of linux kernel
On 08/30/2012 12:15 PM, Sachin Agarwalla wrote:
> Dear Sir/Madam,
> I have some questions on development of linux kernel as follows:-
> 1.I want to know the location of files in linux kernel source code that contains timer initialization and scheduler part.
Scheduler source code is in kernel/sched/* files.
> 2.Also I want to know location of header files(or library files) that are present in the above files.
include/linux/sched.h
> 3.Is there any version of linux kernel that uses openmp or inteltbb or parallelc tool.
No, kernel doesn't use any libraries including libc.
prev parent reply other threads:[~2012-09-04 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <377703089.3951.1346238221003.JavaMail.root@mailstore2.iitkgp.ac.in>
2012-08-30 4:15 ` need help on development of linux kernel Sachin Agarwalla
2012-08-30 8:32 ` anish singh
2012-09-04 6:59 ` Cong Wang
2012-09-04 9:10 ` Sachin Agarwalla [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=1283617617.10114.1346749808002.JavaMail.root@mailstore2.iitkgp.ac.in \
--to=sachin.agarwalla@cse.iitkgp.ernet.in \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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).