[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YJ6YnJv99AEdu0it@hirez.programming.kicks-ass.net>
Date: Fri, 14 May 2021 17:34:52 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Liam Howlett <liam.howlett@...cle.com>
Cc: "maple-tree@...ts.infradead.org" <maple-tree@...ts.infradead.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Song Liu <songliubraving@...com>,
Davidlohr Bueso <dave@...olabs.net>,
"Paul E . McKenney" <paulmck@...nel.org>,
Matthew Wilcox <willy@...radead.org>,
Laurent Dufour <ldufour@...ux.ibm.com>,
David Rientjes <rientjes@...gle.com>,
Axel Rasmussen <axelrasmussen@...gle.com>,
Suren Baghdasaryan <surenb@...gle.com>,
Vlastimil Babka <vbabka@...e.cz>,
Rik van Riel <riel@...riel.com>,
Michel Lespinasse <walken.cr@...il.com>
Subject: Re: [PATCH 26/94] Maple Tree: Add new data structure
On Fri, May 14, 2021 at 05:32:15PM +0200, Peter Zijlstra wrote:
> On Wed, Apr 28, 2021 at 03:36:02PM +0000, Liam Howlett wrote:
> > +static inline unsigned long mte_pivot(const struct maple_enode *mn,
> > + unsigned char piv)
> > +{
> > + struct maple_node *node = mte_to_node(mn);
> > +
> > + switch (mte_node_type(mn)) {
> > + case maple_arange_64:
> > + return node->ma64.pivot[piv];
> > + case maple_range_64:
> > + case maple_leaf_64:
> > + return node->mr64.pivot[piv];
> > + case maple_dense:
> > + default:
> > + return 0;
> > + }
> > +}
Why is @piv 'unsigned char' ? Does that actually generate better code on
any architecture?
At the same time; there's no bounds check.
Powered by blists - more mailing lists