From: Yue Hu <zbestahu@gmail.com>
To: Gao Xiang <hsiangkao@linux.alibaba.com>
Cc: Yue Hu <huyue2@coolpad.com>,
linux-erofs@lists.ozlabs.org, zhangwen@coolpad.com
Subject: Re: [PATCH] erofs-utils: avoid unnecessary insert behavior when not deduplicating
Date: Fri, 14 Oct 2022 09:48:46 +0800 [thread overview]
Message-ID: <20221014094846.00005bdb.zbestahu@gmail.com> (raw)
In-Reply-To: <Y0fTbmoezlKid246@B-P7TQMD6M-0146.local>
On Thu, 13 Oct 2022 16:59:26 +0800
Gao Xiang <hsiangkao@linux.alibaba.com> wrote:
> Hi Yue,
>
> On Thu, Oct 13, 2022 at 12:00:11PM +0800, Yue Hu wrote:
> > From: Yue Hu <huyue2@coolpad.com>
> >
> > We should do nothing in dedupe inserting when it's not configured.
> >
> > Signed-off-by: Yue Hu <huyue2@coolpad.com>
> > ---
>
> Thanks for the patch, do you observe some strange happening?
I can see malloc/memcpy at runtime when dedupe is disabled. So, just skip.
>
> IMO, If dedupe is not enabled, window_size will be 0 I think.
> However, I think we might need to disable it explicitly like below.
>
> So,
> Reviewed-by: Gao Xiang <hsiangkao@linux.alibaba.com>
>
> Thanks,
> Gao Xiang
>
>
> > lib/dedupe.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/lib/dedupe.c b/lib/dedupe.c
> > index 7962014..9cad905 100644
> > --- a/lib/dedupe.c
> > +++ b/lib/dedupe.c
> > @@ -99,7 +99,7 @@ int z_erofs_dedupe_insert(struct z_erofs_inmem_extent *e,
> > {
> > struct z_erofs_dedupe_item *di;
> >
> > - if (e->length < window_size)
> > + if (!dedupe_subtree || e->length < window_size)
> > return 0;
> >
> > di = malloc(sizeof(*di) + e->length - window_size);
> > --
> > 2.17.1
next prev parent reply other threads:[~2022-10-14 1:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 4:00 [PATCH] erofs-utils: avoid unnecessary insert behavior when not deduplicating Yue Hu
2022-10-13 8:59 ` Gao Xiang
2022-10-14 1:48 ` Yue Hu [this message]
2022-10-14 2:15 ` Gao Xiang
2022-10-14 8:44 ` Yue Hu
2022-10-14 9:46 ` Gao Xiang
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=20221014094846.00005bdb.zbestahu@gmail.com \
--to=zbestahu@gmail.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=huyue2@coolpad.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=zhangwen@coolpad.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