From: <lsahn@wewakecorp.com>
To: "'JaeJoon Jung'" <rgbi3307@gmail.com>
Cc: "'Linus Torvalds'" <torvalds@linux-foundation.org>,
"'Sasha Levin'" <levinsasha928@gmail.com>,
"'Liam R . Howlett'" <Liam.Howlett@oracle.com>,
"'Matthew Wilcox'" <willy@infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<maple-tree@lists.infradead.org>, <linux-fsdevel@vger.kernel.org>
Subject: RE: [PATCH v2 1/2] lib/htree: Add locking interface to new Hash Tree
Date: Wed, 7 Aug 2024 10:42:09 +0900 [thread overview]
Message-ID: <000001dae86b$04955090$0dbff1b0$@wewakecorp.com> (raw)
In-Reply-To: <CAHOvCC7OLfXSN-dExxSFrPACj3sd09TAgrjT1eC96idKirrVJw@mail.gmail.com>
> -----Original Message-----
> From: owner-linux-mm@kvack.org <owner-linux-mm@kvack.org> On Behalf Of
> JaeJoon Jung
> Sent: Wednesday, August 7, 2024 9:22 AM
> To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Linus Torvalds <torvalds@linux-foundation.org>; Sasha Levin
> <levinsasha928@gmail.com>; Liam R . Howlett <Liam.Howlett@oracle.com>;
> Matthew Wilcox <willy@infradead.org>; linux-kernel@vger.kernel.org; linux-
> mm@kvack.org; maple-tree@lists.infradead.org; linux-
> fsdevel@vger.kernel.org
> Subject: Re: [PATCH v2 1/2] lib/htree: Add locking interface to new Hash
> Tree
...
> The Hash Tree I implemented manages the Tree with the characteristic
> of a hash that is accessed in O(1).
> Even if the tree gets deeper, the search time does not increase.
> There is no rotation cost because the tree is kept balanced by hash key.
How does it keep balancing?
next prev parent reply other threads:[~2024-08-07 1:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 10:01 [PATCH v2 1/2] lib/htree: Add locking interface to new Hash Tree JaeJoon Jung
2024-08-05 18:33 ` Greg Kroah-Hartman
2024-08-06 7:07 ` Greg Kroah-Hartman
2024-08-06 7:32 ` JaeJoon Jung
2024-08-06 7:38 ` Greg Kroah-Hartman
2024-08-07 0:21 ` JaeJoon Jung
2024-08-07 1:10 ` Pedro Falcato
2024-08-07 1:42 ` lsahn [this message]
2024-08-07 2:24 ` JaeJoon Jung
2024-08-07 3:48 ` Matthew Wilcox
2024-08-07 22:13 ` JaeJoon Jung
2024-08-07 1:16 ` Darrick J. Wong
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='000001dae86b$04955090$0dbff1b0$@wewakecorp.com' \
--to=lsahn@wewakecorp.com \
--cc=Liam.Howlett@oracle.com \
--cc=levinsasha928@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.org \
--cc=rgbi3307@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).