From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Steve French <smfltc@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-cifs-client@lists.samba.org,
jra@samba.org
Subject: Re: [PATCH COW] sys_copyfile
Date: Tue, 27 Apr 2004 18:42:20 +0200 [thread overview]
Message-ID: <20040427164220.GB2176@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <1083081505.12804.65.camel@stevef95.austin.ibm.com>
On Tue, 27 April 2004 10:58:25 -0500, Steve French wrote:
>
> > With warm cache, copyfile() is about 10% faster
>
> Over the network it would be a lot more than that.
True, if network traffic is saved as well.
> in do_copyfile all I would need would be an op that looks a bit like
> rename (the cifs vfs part of the changes, to fs/cifs/cifssmb.c mostly,
> would be trivial) e.g.:
>
> int do_copyfile(struct nameidata *old_nd, struct nameidata *new_nd,
> struct dentry *new_dentry, umode_t mode)
> {
> - int ret;
> + int ret = 0;
>
> if (!old_nd->dentry->d_inode)
> return -ENOENT;
> if (!S_ISREG(old_nd->dentry->d_inode->i_mode))
> return -EINVAL;
> /* FIXME: replace with proper permission check */
> if (new_dentry->d_inode)
> return -EEXIST;
>
> + if(old_nd->dentry->d_inode->i_op->copy) {
> + ret = old_dir->i_op->copy(old_nd->dentry,
> + mode, new_dentry);
> + }
Shouldn't it be rather
if (old_nd->dentry->d_inode->i_op->copy)
return old_nd->dentry->d_inode->i_op->copy(old_nd->dentry,
mode, new_dentry);
or something similar? The copy() effectively replaces the complete
create/sendfile/possibly-unlink series.
>
> if(!ret)
> return ret;
> else
> ret = vfs_create(new_nd->dentry->d_inode,
> new_dentry, mode, new_nd);
> if (ret)
> return ret;
>
> ret = copy_data(old_nd->dentry, old_nd->mnt, new_dentry,
> new_nd->mnt);
>
> if (ret) {
> int error = vfs_unlink(new_nd->dentry->d_inode,
> new_dentry);
> BUG_ON(error);
> /* FIXME: not sure if there are return value we
> should not BUG()
> * on */
> }
> return ret;
> }
>
Jörn
--
The grand essentials of happiness are: something to do, something to
love, and something to hope for.
-- Allan K. Chalmers
next prev parent reply other threads:[~2004-04-27 16:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 15:58 Steve French
2004-04-27 16:42 ` Jörn Engel [this message]
2004-04-27 19:46 ` Steve French
2004-04-27 19:55 ` Jörn Engel
-- strict thread matches above, loose matches on Subject: below --
2004-04-26 9:20 Jörn Engel
2004-04-27 11:30 ` Erik Mouw
2004-04-27 11:47 ` 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=20040427164220.GB2176@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=jra@samba.org \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smfltc@us.ibm.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
all inboxes | Powered by JetHome®