From: Simon Horman <horms@kernel.org>
To: "Bo Liu (刘波)-浪潮信息" <liubo03@inspur.com>
Cc: "miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
"alex.aring@gmail.com" <alex.aring@gmail.com>,
"stefan@datenfreihafen.org" <stefan@datenfreihafen.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"linux-wpan@vger.kernel.org" <linux-wpan@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net: ieee802154: at86rf230: convert to use maple tree register cache
Date: Sun, 4 Feb 2024 14:35:13 +0000 [thread overview]
Message-ID: <20240204143513.GB941651@kernel.org> (raw)
In-Reply-To: <982c399a2bd043a186a27a399f9b2493@inspur.com>
On Fri, Feb 02, 2024 at 08:08:14AM +0000, Bo Liu (刘波)-浪潮信息 wrote:
>
> >Hi Bo,
> >
> >liubo03@inspur.com wrote on Fri, 2 Feb 2024 01:45:12 -0500:
> >
> >> The maple tree register cache is based on a much more modern data
> >> structure than the rbtree cache and makes optimisation choices which
> >> are probably more appropriate for modern systems than those made by the
> >rbtree cache.
> >
> >What are the real intended benefits? Shall we expect any drawbacks?
> >
> Hi
> The maple tree register cache has now got to the point where is is
> roughly feature compatible with the rbtree cache. It's based on a much more modern data
> structure than the rbtree cache
Thanks Bo Liu,
You have stated that maple is more modern than rbtree.
But please address Miquel's questions: what are the real
expected benefits; what possible drawbacks are there?
next prev parent reply other threads:[~2024-02-04 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 8:08 [PATCH] net: ieee802154: at86rf230: convert to use maple tree register cache Bo Liu (刘波)-浪潮信息
2024-02-04 14:35 ` Simon Horman [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-02 6:45 Bo Liu
2024-02-02 7:55 ` Miquel Raynal
2024-02-05 19:42 ` Alexander Aring
2024-02-06 9:25 ` Miquel Raynal
2024-02-20 10:04 ` Miquel Raynal
2024-02-26 20:48 ` Stefan Schmidt
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=20240204143513.GB941651@kernel.org \
--to=horms@kernel.org \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=liubo03@inspur.com \
--cc=miquel.raynal@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stefan@datenfreihafen.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).