From: Clemens Koller <clemens.koller@anagramm.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: shaneed cm <just4kernel@gmail.com>, linux-kernel@vger.kernel.org
Subject: OT: Re: request for Linux kernel related project ideas
Date: Thu, 23 Aug 2007 14:35:05 +0200 [thread overview]
Message-ID: <46CD7EF9.5000802@anagramm.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0708230757330.4181@localhost.localdomain>
Robert P. J. Day schrieb:
> On Thu, 23 Aug 2007, Clemens Koller wrote:
>
>> shaneed cm schrieb:
>>> Hi,
>>> This is a request for Linux kernel related project ideas.
>>> I am Computer Science Engineering final year student. We have to do
>>> a project of one year duration . I formed a group of two and we
>>> decided to do a project in Linux kernel. Our interests are in Virtual
>>> memory management, file system, process scheduling and load balancing
>>> in Linux clusters. Last year we did a study of Linux's page
>>> replacement mechanism. As I am not experienced as you people, please
>>> suggest me some ideas.
>> Just for an example:
>> Checkout what filesystem / caching / scheduling policy is most
>> suitable for Solid State PATA/SATA Flashdisks and write / modify
>> a kernel scheduler to support it.
>
> i'm not sure that it's appropriate for LKML folks to be giving anyone
> suggestions for projects.
I don't care so much. The answer should have been a hint that
just some minutes ago, we had a thread on this list about
Solid State Flash disks... it could be interesting to
spend some brain cells in that area - just for an example
...and there are so many.
> the eventual choice of project should be
> based on what *shaneed* wants, not what other people tell him he
> should be doing.
Propably he doesn't know yet what he wants?
> in addition, sometimes part of the work involved in a school project
> involves doing enough research to just make the *choice*. what
> shaneed is asking is that others do that work for him. IMHO, he
> should be told politely but firmly that selecting a topic is *his*
> problem. that's just part of the academic process.
Asking people with more experience what's needed is in my point
of view also a reasonably academic process to make progress in the
right direction. IMHO that's one of the main reasons why
open projects work.
Regards,
--
Clemens Koller
__________________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Straße 45/1
Linhof Werksgelände
D-81379 München
Tel.089-741518-50
Fax 089-741518-19
http://www.anagramm-technology.com
next prev parent reply other threads:[~2007-08-23 12:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 8:10 request for Linux kernel related project ideas shaneed cm
2007-08-23 12:00 ` Clemens Koller
2007-08-23 12:00 ` Robert P. J. Day
2007-08-23 12:35 ` Clemens Koller [this message]
2007-08-23 15:55 ` linux-os (Dick Johnson)
2007-08-23 16:04 ` Robert P. J. Day
2007-08-29 18:12 ` Bill Davidsen
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=46CD7EF9.5000802@anagramm.de \
--to=clemens.koller@anagramm.de \
--cc=just4kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.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