From: Peter Zijlstra <peterz@infradead.org>
To: Marc Gonzalez <marc.w.gonzalez@free.fr>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rafael Wysocki <rjw@rjwysocki.net>,
LKML <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Robin Murphy <robin.murphy@arm.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Alexey Brodkin <alexey.brodkin@synopsys.com>,
Will Deacon <will@kernel.org>,
Russell King <rmk+kernel@armlinux.org.uk>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Tejun Heo <tj@kernel.org>, Mark Brown <broonie@kernel.org>
Subject: Re: [RFC PATCH v1] devres: align devres.data strictly only for devm_kmalloc()
Date: Fri, 20 Dec 2019 18:19:06 +0100 [thread overview]
Message-ID: <20191220171906.GR2827@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <5b12b473-bf9a-6dc9-838c-f9312eb10635@free.fr>
On Fri, Dec 20, 2019 at 01:05:43PM +0100, Marc Gonzalez wrote:
> If "fixing" the kmalloc strict alignment requirement on arm64 is too
> hard, maybe it would be possible to shave some of the devm memory
> waste by working with (chained) arrays of devm nodes, instead
> of a straight-up linked list. (Akin to a C++ vector) Removal would
> be expensive, but that's supposed to be a rare operation, right?
xarray might be what you're looking for.
next prev parent reply other threads:[~2019-12-20 17:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 15:30 Marc Gonzalez
2019-12-17 15:45 ` Greg Kroah-Hartman
2019-12-17 16:17 ` Marc Gonzalez
2019-12-18 14:20 ` Alexey Brodkin
2019-12-18 15:40 ` Marc Gonzalez
2019-12-20 10:19 ` Marc Gonzalez
2019-12-20 10:22 ` Greg Kroah-Hartman
2019-12-20 10:22 ` Greg Kroah-Hartman
2019-12-20 12:05 ` Marc Gonzalez
2019-12-20 17:19 ` Peter Zijlstra [this message]
2019-12-20 14:06 ` Peter Zijlstra
2019-12-20 14:16 ` Greg Kroah-Hartman
2019-12-20 15:01 ` Robin Murphy
2019-12-20 17:13 ` Peter Zijlstra
2019-12-20 22:02 ` Robin Murphy
2020-01-06 10:05 ` Peter Zijlstra
2019-12-20 19:32 ` Alexey Brodkin
2019-12-20 20:23 ` Peter Zijlstra
2019-12-20 21:02 ` Alexey Brodkin
2019-12-20 21:47 ` Dmitry Torokhov
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=20191220171906.GR2827@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=alexey.brodkin@synopsys.com \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.w.gonzalez@free.fr \
--cc=rjw@rjwysocki.net \
--cc=rmk+kernel@armlinux.org.uk \
--cc=robin.murphy@arm.com \
--cc=tj@kernel.org \
--cc=will@kernel.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
Powered by JetHome