From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: linux-kernel@vger.kernel.org
Cc: Jamie Lokier <jamie@shareable.org>, Pavel Machek <pavel@ucw.cz>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Subject: [ANNOUNCEMENT PATCH COW] proof of concept impementation of cowlinks
Date: Thu, 6 May 2004 15:17:31 +0200 [thread overview]
Message-ID: <20040506131731.GA7930@wohnheim.fh-wedel.de> (raw)
Couldn't sleep last night and finished a first complete version of
cowlinks, code-named MAD COW. It is still based on the stupid old
design with a flag to distinguish between regular hard links and
cowlinks. Please don't comment on that design, it's just a proof of
concept.
Patches are against 2.6.5 but most things should apply to other 2.6
kernel without too much trouble.
1 generic_sendpage - allow sendfile with ext[23] files as target
2 sendfile - introduce vfs_sendfile for in-kernel use
3 copyfile - new copyfile() system call
4 lock_flags - old cruft, just ignore it
5 madcow - the MAD COW itself
Patches 1-3 will stay, 4 will be remove and 5 replaced by a better
design over time. I've also set up a webpage for it:
http://wohnheim.fh-wedel.de/~joern/cowlink/
Maybe that should be converted into a wiki so someone with better
taste than myself can improve it.
Jörn
--
This above all: to thine own self be true.
-- Shakespeare
next reply other threads:[~2004-05-06 13:21 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 13:17 Jörn Engel [this message]
2004-05-06 13:18 ` [PATCH COW] generic_sendpage Jörn Engel
2004-05-06 13:19 ` [PATCH COW] sendfile Jörn Engel
2004-05-06 13:19 ` [PATCH COW] copyfile Jörn Engel
2004-05-06 13:20 ` [PATCH COW] lock_flags Jörn Engel
2004-05-06 13:21 ` [PATCH COW] MAD COW Jörn Engel
2004-05-08 13:45 ` [ANNOUNCEMENT PATCH COW] proof of concept impementation of cowlinks Denis Vlasenko
2004-05-08 22:10 ` Pavel Machek
2004-05-09 14:09 ` Denis Vlasenko
2004-05-09 21:53 ` Pavel Machek
2004-05-10 15:44 ` Jörn Engel
2004-05-10 15:51 ` Pavel Machek
2004-05-10 15:56 ` Jörn Engel
2004-05-12 0:26 ` Jamie Lokier
2004-05-13 10:56 ` Jörn Engel
2004-05-12 20:29 ` Rob Landley
2004-05-08 22:48 ` Pavel Machek
2004-05-10 15:53 ` Jörn Engel
2004-05-10 19:26 ` Jan Harkes
2004-05-11 10:02 ` Jörn Engel
2004-05-11 14:08 ` Jan Harkes
2004-05-11 14:18 ` Jan Harkes
2004-05-11 14:33 ` Jörn Engel
2004-05-21 23:23 ` Rob Landley
2004-05-25 22:46 ` Jan Harkes
2004-05-11 15:40 ` Steve French
2004-05-11 15:58 ` Jörn Engel
2004-05-10 5:15 ` Eric W. Biederman
2004-05-10 15:59 ` Jörn Engel
2004-05-12 16:39 ` Rob Landley
2004-05-20 13:49 ` Pavel Machek
2004-05-25 21:55 ` Rob Landley
2004-05-25 22:08 ` Pavel Machek
2004-05-25 23:16 ` Rob Landley
2004-05-26 0:16 ` Ian Stirling
2004-05-26 9:52 ` Jörn Engel
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=20040506131731.GA7930@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=ebiederm@xmission.com \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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®