From: Jan Kara <jack@suse.cz>
To: Chao Yu <chao2.yu@samsung.com>
Cc: jack@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev][PATCH v2] udf: avoid redundant memcpy when writing data in ICB
Date: Tue, 15 Jul 2014 16:35:21 +0200 [thread overview]
Message-ID: <20140715143521.GC1733@quack.suse.cz> (raw)
In-Reply-To: <000d01cf9fcd$9e226500$da672f00$@samsung.com>
On Tue 15-07-14 09:38:51, Chao Yu wrote:
> Valid data within i_size in page cache will be copied to ICB cache when we
> writeback the page by invoking udf_adinicb_writepage, so the copy in
> udf_adinicb_write_end is redundant.
> After we remove the copy, it's better to use simple_write_end directly in
> udf_adinicb_aops instead of udf_adinicb_write_end.
>
> v2:
> o fix to remove redundant code correctly and use simple_write_end directly in
> udf_adinicb_aops pointed out by Jan Kara.
Thanks! I've merged the patch.
Honza
>
> Signed-off-by: Chao Yu <chao2.yu@samsung.com>
> ---
> fs/udf/file.c | 20 +-------------------
> 1 file changed, 1 insertion(+), 19 deletions(-)
>
> diff --git a/fs/udf/file.c b/fs/udf/file.c
> index d80738f..3d06489 100644
> --- a/fs/udf/file.c
> +++ b/fs/udf/file.c
> @@ -100,24 +100,6 @@ static int udf_adinicb_write_begin(struct file *file,
> return 0;
> }
>
> -static int udf_adinicb_write_end(struct file *file,
> - struct address_space *mapping,
> - loff_t pos, unsigned len, unsigned copied,
> - struct page *page, void *fsdata)
> -{
> - struct inode *inode = mapping->host;
> - unsigned offset = pos & (PAGE_CACHE_SIZE - 1);
> - char *kaddr;
> - struct udf_inode_info *iinfo = UDF_I(inode);
> -
> - kaddr = kmap_atomic(page);
> - memcpy(iinfo->i_ext.i_data + iinfo->i_lenEAttr + offset,
> - kaddr + offset, copied);
> - kunmap_atomic(kaddr);
> -
> - return simple_write_end(file, mapping, pos, len, copied, page, fsdata);
> -}
> -
> static ssize_t udf_adinicb_direct_IO(int rw, struct kiocb *iocb,
> struct iov_iter *iter,
> loff_t offset)
> @@ -130,7 +112,7 @@ const struct address_space_operations udf_adinicb_aops = {
> .readpage = udf_adinicb_readpage,
> .writepage = udf_adinicb_writepage,
> .write_begin = udf_adinicb_write_begin,
> - .write_end = udf_adinicb_write_end,
> + .write_end = simple_write_end,
> .direct_IO = udf_adinicb_direct_IO,
> };
>
> --
> 2.0.1.474.g72c7794
>
>
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2014-07-15 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 1:38 Chao Yu
2014-07-15 14:35 ` Jan Kara [this message]
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=20140715143521.GC1733@quack.suse.cz \
--to=jack@suse.cz \
--cc=chao2.yu@samsung.com \
--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®