From: Pavel Machek <pavel@suse.cz>
To: Yuri Niyazov <yuricake@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What does the linux kernel need?
Date: Sat, 1 Jan 2000 00:43:02 +0000 [thread overview]
Message-ID: <20000101004302.A45@(none)> (raw)
In-Reply-To: <20010215171245.21445.qmail@web2301.mail.yahoo.com>
In-Reply-To: <20010215171245.21445.qmail@web2301.mail.yahoo.com>; from yuricake@yahoo.com on Thu, Feb 15, 2001 at 09:12:45AM -0800
Hi!
> Hello, respected Linux kernel developers,
> I am currently a university student taking a "Advanced design of
> Operating Systems" class at
> New York University. We are reviewing some basic and studying a few
> advanced issues with regards
> to kernel design, mostly multithreading, scalability, performance
> improvement - its webpage is http://www.scs.cs.nyu.edu/G22.3033-010/
> take a look if you please. The requirement of the class is a final
> project proposal and
> implementation of a student's own choosing - I would really like to do
> something useful for the
> linux kernel, but I do not know what kinds of issues are most imminent
> at the linux kernel and
> have to be worked on. I would greatly appreciate it if people would
> send me ideas of what is
Creating network character device (similar to nbd) would make some people
happy. Pavel
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
next prev parent reply other threads:[~2001-02-23 8:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 17:12 What does the linux kernel need? Yuri Niyazov
2000-01-01 0:43 ` Pavel Machek [this message]
2001-02-23 19:14 ` problem with mount -o loop Tim Tim
2001-02-23 19:22 ` J Sloan
2001-02-16 12:41 ` What does the linux kernel need? Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2001-02-15 19:47 Gabi Davar
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='20000101004302.A45@(none)' \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=yuricake@yahoo.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