From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [PATCH] f2fs: add a way to turn off ipu bio cache
Date: Wed, 8 Jan 2020 20:23:15 +0800 [thread overview]
Message-ID: <d5555fd8-736f-cc2f-1e57-d9ac01b3d012@huawei.com> (raw)
In-Reply-To: <20200108120444.GC28331@jaegeuk-macbookpro.roam.corp.google.com>
On 2020/1/8 20:04, Jaegeuk Kim wrote:
> On 01/08, Chao Yu wrote:
>> On 2020/1/7 10:07, Jaegeuk Kim wrote:
>>> Setting 0x40 in /sys/fs/f2fs/dev/ipu_policy gives a way to turn off
>>> bio cache, which is useufl to check whether block layer using hardware
>>> encryption engine merges IOs correctly.
>>>
>>> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
>>> ---
>>> Documentation/filesystems/f2fs.txt | 1 +
>>> fs/f2fs/segment.c | 2 +-
>>> fs/f2fs/segment.h | 1 +
>>> 3 files changed, 3 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/Documentation/filesystems/f2fs.txt b/Documentation/filesystems/f2fs.txt
>>> index 41b5aa94b30f..cd93bcc34726 100644
>>> --- a/Documentation/filesystems/f2fs.txt
>>> +++ b/Documentation/filesystems/f2fs.txt
>>> @@ -335,6 +335,7 @@ Files in /sys/fs/f2fs/<devname>
>>> 0x01: F2FS_IPU_FORCE, 0x02: F2FS_IPU_SSR,
>>> 0x04: F2FS_IPU_UTIL, 0x08: F2FS_IPU_SSR_UTIL,
>>> 0x10: F2FS_IPU_FSYNC.
>>
>> . -> ,
>
> Actually, we can't do it. I revised it a bit instead.
One more question, why skipping 0x20 bit position?
Thanks,
>
>>
>> Reviewed-by: Chao Yu <yuchao0@huawei.com>
>>
>> Thanks,
>>
>>> + 0x40: F2FS_IPU_NOCACHE disables bio caches.
>>>
>>> min_ipu_util This parameter controls the threshold to trigger
>>> in-place-updates. The number indicates percentage
>>> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
>>> index a9519532c029..311fe4937f6a 100644
>>> --- a/fs/f2fs/segment.c
>>> +++ b/fs/f2fs/segment.c
>>> @@ -3289,7 +3289,7 @@ int f2fs_inplace_write_data(struct f2fs_io_info *fio)
>>>
>>> stat_inc_inplace_blocks(fio->sbi);
>>>
>>> - if (fio->bio)
>>> + if (fio->bio && !(SM_I(sbi)->ipu_policy & (1 << F2FS_IPU_NOCACHE)))
>>> err = f2fs_merge_page_bio(fio);
>>> else
>>> err = f2fs_submit_page_bio(fio);
>>> diff --git a/fs/f2fs/segment.h b/fs/f2fs/segment.h
>>> index a1b3951367cd..02e620470eef 100644
>>> --- a/fs/f2fs/segment.h
>>> +++ b/fs/f2fs/segment.h
>>> @@ -623,6 +623,7 @@ enum {
>>> F2FS_IPU_SSR_UTIL,
>>> F2FS_IPU_FSYNC,
>>> F2FS_IPU_ASYNC,
>>> + F2FS_IPU_NOCACHE,
>>> };
>>>
>>> static inline unsigned int curseg_segno(struct f2fs_sb_info *sbi,
>>>
> .
>
next prev parent reply other threads:[~2020-01-08 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 2:07 Jaegeuk Kim
2020-01-08 7:59 ` [f2fs-dev] " Chao Yu
2020-01-08 12:04 ` Jaegeuk Kim
2020-01-08 12:23 ` Chao Yu [this message]
2020-01-08 23:18 ` Jaegeuk Kim
2020-01-11 9:26 ` 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=d5555fd8-736f-cc2f-1e57-d9ac01b3d012@huawei.com \
--to=yuchao0@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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®