From: Jaegeuk Kim via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: Introduce linear search for dentries
Date: Mon, 6 Jan 2025 21:18:26 +0000 [thread overview]
Message-ID: <Z3xIojPamtc5-dUd@google.com> (raw)
In-Reply-To: <Z3eswqllW9LX2XMh@infradead.org>
On 01/03, Christoph Hellwig wrote:
> On Mon, Dec 23, 2024 at 04:57:35PM +0000, Jaegeuk Kim wrote:
> > > That means you have really bad worst case behavior for negative lookups.
> > > I don' think this is in any way a good idea.
> >
> > No surprise. Please check:
> > https://lore.kernel.org/lkml/Z1mzu4Eg6CPURra3@google.com/
>
> Well, I think Linus finally gave in to revert the offending commit
> after the usual case insensitivity rants?
In any ways, we need a way to give the files back for customers, which is only
doable by the linear search, whether it sucks or not. :(
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Daniel Lee <chullee@google.com>, Chao Yu <chao@kernel.org>,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] f2fs: Introduce linear search for dentries
Date: Mon, 6 Jan 2025 21:18:26 +0000 [thread overview]
Message-ID: <Z3xIojPamtc5-dUd@google.com> (raw)
In-Reply-To: <Z3eswqllW9LX2XMh@infradead.org>
On 01/03, Christoph Hellwig wrote:
> On Mon, Dec 23, 2024 at 04:57:35PM +0000, Jaegeuk Kim wrote:
> > > That means you have really bad worst case behavior for negative lookups.
> > > I don' think this is in any way a good idea.
> >
> > No surprise. Please check:
> > https://lore.kernel.org/lkml/Z1mzu4Eg6CPURra3@google.com/
>
> Well, I think Linus finally gave in to revert the offending commit
> after the usual case insensitivity rants?
In any ways, we need a way to give the files back for customers, which is only
doable by the linear search, whether it sucks or not. :(
next prev parent reply other threads:[~2025-01-06 21:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 17:21 [f2fs-dev] [PATCH v2] f2fs: Introduce linear search for dentries Daniel Lee via Linux-f2fs-devel
2024-12-20 17:21 ` Daniel Lee
2024-12-20 21:00 ` [f2fs-dev] " Jaegeuk Kim via Linux-f2fs-devel
2024-12-20 21:00 ` Jaegeuk Kim
2024-12-23 8:26 ` [f2fs-dev] " Christoph Hellwig
2024-12-23 8:26 ` Christoph Hellwig
2024-12-23 16:57 ` [f2fs-dev] " Jaegeuk Kim via Linux-f2fs-devel
2024-12-23 16:57 ` Jaegeuk Kim
2025-01-03 9:24 ` [f2fs-dev] " Christoph Hellwig
2025-01-03 9:24 ` Christoph Hellwig
2025-01-06 21:18 ` Jaegeuk Kim via Linux-f2fs-devel [this message]
2025-01-06 21:18 ` Jaegeuk Kim
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=Z3xIojPamtc5-dUd@google.com \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=hch@infradead.org \
--cc=jaegeuk@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.