From: Liam Howlett <liam.howlett@oracle.com>
To: David Laight <David.Laight@ACULAB.COM>
Cc: "maple-tree@lists.infradead.org" <maple-tree@lists.infradead.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>, Yu Zhao <yuzhao@google.com>
Subject: Re: [PATCH] maple_tree: Do not inline write slow path
Date: Thu, 21 Jul 2022 19:30:13 +0000 [thread overview]
Message-ID: <20220721193007.cmpdocvvmox6gktf@revolver> (raw)
In-Reply-To: <040322fa455941ff9b82ebb0f53a576a@AcuMS.aculab.com>
* David Laight <David.Laight@ACULAB.COM> [220721 04:26]:
> From: Liam Howlett
> > Sent: 21 July 2022 01:53
> >
> > Having the slow path inlined causes too much stack usage. Create new
> > function mas_wr_bnode() to write a big node into the tree
>
> Unless you mark the function 'noinline' the compiler is
> likely to inline it anyway.
>
> David
Thanks for looking at this.
On my testing, removing the inline allowed the compiler to stop
complaining about the stack frame size. I don't mind if it is inlined,
but I don't want to force it to be inlined. I'd like to let the
compiler decide if it does the right thing.
Thanks,
Liam
>
> >
> > Signed-off-by: Liam R. Howlett <Liam.Howlett@oracle.com>
> > ---
> > lib/maple_tree.c | 22 +++++++++++++++++-----
> > 1 file changed, 17 insertions(+), 5 deletions(-)
> >
> > diff --git a/lib/maple_tree.c b/lib/maple_tree.c
> > index 95d8659c5a99..4c383c780162 100644
> > --- a/lib/maple_tree.c
> > +++ b/lib/maple_tree.c
> > @@ -4297,12 +4297,27 @@ static inline bool mas_wr_append(struct ma_wr_state *wr_mas)
> > return false;
> > }
> >
> > +/*
> > + * mas_wr_bnode() - Slow path for a modification.
> > + * @wr_mas: The write maple state
> > + *
> > + * This is where split, rebalance end up.
> > + */
> > +static void mas_wr_bnode(struct ma_wr_state *wr_mas)
> > +{
> > + struct maple_big_node b_node;
> > +
> > + trace_ma_write(__func__, wr_mas->mas, 0, wr_mas->entry);
> > + memset(&b_node, 0, sizeof(struct maple_big_node));
> > + mas_store_b_node(wr_mas, &b_node, wr_mas->offset_end);
> > + mas_commit_b_node(wr_mas, &b_node, wr_mas->node_end);
> > +}
> > +
> > static inline void mas_wr_modify(struct ma_wr_state *wr_mas)
> > {
> > unsigned char node_slots;
> > unsigned char node_size;
> > struct ma_state *mas = wr_mas->mas;
> > - struct maple_big_node b_node;
> >
> > /* Direct replacement */
> > if (wr_mas->r_min == mas->index && wr_mas->r_max == mas->last) {
> > @@ -4338,10 +4353,7 @@ static inline void mas_wr_modify(struct ma_wr_state *wr_mas)
> > return;
> >
> > slow_path:
> > - memset(&b_node, 0, sizeof(struct maple_big_node));
> > - mas_store_b_node(wr_mas, &b_node, wr_mas->offset_end);
> > - trace_ma_write(__func__, mas, 0, wr_mas->entry);
> > - mas_commit_b_node(wr_mas, &b_node, wr_mas->node_end);
> > + mas_wr_bnode(wr_mas);
> > }
> >
> > /*
> > --
> > 2.35.1
>
> -
> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
> Registration No: 1397386 (Wales)
>
prev parent reply other threads:[~2022-07-21 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 0:53 Liam Howlett
2022-07-21 8:26 ` David Laight
2022-07-21 19:30 ` Liam Howlett [this message]
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=20220721193007.cmpdocvvmox6gktf@revolver \
--to=liam.howlett@oracle.com \
--cc=David.Laight@ACULAB.COM \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.org \
--cc=yuzhao@google.com \
/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