The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <yuchao0@huawei.com>
Cc: linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, chao@kernel.org
Subject: Re: [PATCH] f2fs: restrict write IO alignment condition
Date: Fri, 10 Mar 2017 10:50:05 -0800	[thread overview]
Message-ID: <20170310185005.GC22979@jaegeuk.local> (raw)
In-Reply-To: <20170310093804.35928-1-yuchao0@huawei.com>

On 03/10, Chao Yu wrote:
> We should only align start offset of bio with defined IO_SIZE for below
> conditions:
> a. write IOs
> b. Out-place-update
> c. non-meta page
> 
> Signed-off-by: Chao Yu <yuchao0@huawei.com>
> ---
>  fs/f2fs/data.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> index 1375fef11146..3e6b0cc5e36a 100644
> --- a/fs/f2fs/data.c
> +++ b/fs/f2fs/data.c
> @@ -395,7 +395,9 @@ int f2fs_submit_page_mbio(struct f2fs_io_info *fio)
>  		__submit_merged_bio(io);
>  alloc_new:
>  	if (io->bio == NULL) {
> -		if ((fio->type == DATA || fio->type == NODE) &&
> +		if (!is_read && (fio->type == DATA || fio->type == NODE) &&
> +				bio_page->mapping != META_MAPPING(sbi) &&

BUG_ON(), since it's covered by fio->type == DATA || fio->type == NODE.

> +				fio->new_blkaddr != fio->old_blkaddr &&

BUG_ON(), since LFS mount option doesn't allow any in-place updates.

>  				fio->new_blkaddr & F2FS_IO_SIZE_MASK(sbi)) {

So, is_read is worth to check?

Thanks,

>  			err = -EAGAIN;
>  			if (!is_read)
> -- 
> 2.8.2.295.g3f1c1d0

  reply	other threads:[~2017-03-10 18:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10  9:38 [PATCH] f2fs: restrict write IO alignment condition Chao Yu
2017-03-10 18:50 ` Jaegeuk Kim [this message]
2017-03-13 12:25   ` Chao Yu

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=20170310185005.GC22979@jaegeuk.local \
    --to=jaegeuk@kernel.org \
    --cc=chao@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuchao0@huawei.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