From: David Chow <davidchow@rcn.com.hk>
To: linux-kernel@vger.kernel.org
Subject: Contribution of the linux kernel development
Date: Sun, 09 Sep 2001 02:43:04 +0800 [thread overview]
Message-ID: <3B9A66B8.D165155B@rcn.com.hk> (raw)
Dear all,
First thanks to Linus who start this wonderful OS and giving out for
free. I am from Hong Kong and I would like to contribute on linux kerenl
developments. I am a newbie to linux kernel hacking. I started on memory
management system as my company is developing a linux native hardware
platform which is a diskless computer. Now I am writing experimental
filesystems using the idea from Erez who wrote the FiST which is a
powerful stackable filesystem. I am now debuging the code from him to
make the filesystem working properly on a production system. My work is
to improve the reliability, performance and manageability of the
platform. That makes me dig in deep into the kernel recently. I
sucessfully ported the code for nfsswap from Justus Heine to kernel from
2.4.0 to 2.4.6 , up to know my system is running 2.4.4 . I also improve
the code a bit to improve some of the overheads and now it is running
fine on the system. But I notice that the sources from the kernel seems
want a future of nfs swap support, but there are not official code for
this at the moment. I have tested the nfsswap code for a couple of
months and reporting no errors at all even under extreme high loaded
ethernet. I would be happy to make myself contributing the kernel
development and supporting the work for nfsswap and FiST . I would like
to share the code with others. If this message is heard by the VFS
maintainer, please contact me. Thanks.
regards,
David Chow
next reply other threads:[~2001-09-08 18:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-08 18:43 David Chow [this message]
2001-09-14 9:24 ` Pavel Machek
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=3B9A66B8.D165155B@rcn.com.hk \
--to=davidchow@rcn.com.hk \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®