From: Miquel Raynal <miquel.raynal@bootlin•com>
To: Alexander Aring <aahringo@redhat•com>
Cc: Bo Liu <liubo03@inspur•com>,
alex.aring@gmail•com, stefan@datenfreihafen•org,
davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
pabeni@redhat•com, linux-wpan@vger•kernel.org,
netdev@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: [PATCH] net: ieee802154: at86rf230: convert to use maple tree register cache
Date: Tue, 20 Feb 2024 11:04:38 +0100 [thread overview]
Message-ID: <20240220110438.247e2746@xps-13> (raw)
In-Reply-To: <CAK-6q+jnZOkSAM8_BQH=CaQhfCQwm0P+segZ+0E6oLeX=BhLHQ@mail.gmail.com>
Hi,
aahringo@redhat•com wrote on Mon, 5 Feb 2024 14:42:09 -0500:
> Hi,
>
> On Fri, Feb 2, 2024 at 2:56 AM Miquel Raynal <miquel.raynal@bootlin•com> 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?
> >
>
> I doubt it has really any benefits, only the slowpath is using regmap
> to set some registers. Maybe if you change phy setting frequently it
> might have an impact, but this isn't even a path considered to run
> fast.
Ok, then let's take the series I guess. For the three patches:
Reviewed-by: Miquel Raynal <miquel.raynal@bootlin•com>
Thanks,
Miquèl
next prev parent reply other threads:[~2024-02-20 10:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 6:45 [PATCH] net: ieee802154: at86rf230: convert to use maple tree register cache 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 [this message]
2024-02-26 20:48 ` Stefan Schmidt
-- strict thread matches above, loose matches on Subject: below --
2024-02-02 8:08 Bo Liu (刘波)-浪潮信息
2024-02-04 14:35 ` Simon Horman
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=20240220110438.247e2746@xps-13 \
--to=miquel.raynal@bootlin$(echo .)com \
--cc=aahringo@redhat$(echo .)com \
--cc=alex.aring@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-wpan@vger$(echo .)kernel.org \
--cc=liubo03@inspur$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=stefan@datenfreihafen$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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