From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
Liam Girdwood <lrg@ti.com>, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 1/2 v2] ASoC: soc-cache: block based rbtree compression
Date: Tue, 3 May 2011 14:44:28 +0100 [thread overview]
Message-ID: <20110503134427.GN1762@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110503114618.GA2215@opensource.wolfsonmicro.com>
On Tue, May 03, 2011 at 12:46:18PM +0100, Dimitris Papastamos wrote:
> We can do this yes. One possible problem is that if we start merging
> blocks like that, in the long run we might end-up having one node with a
> very large block. This will happen for example if we write to the
> entire register map. In that case looking up a register will require
> O(n) time in the worst case where n is the number of registers. If we
> however have a constant limit k on the block size, we can cut this down to
> O(klogn) in the worst case.
Summarising offline discussion for the list: if we use an array for the
data and realloc it if we need to change the node size then we keep the
O(klogn) for these cases
prev parent reply other threads:[~2011-05-03 13:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 12:28 [PATCH 1/2 v2] ASoC: soc-cache: block based rbtree compression Dimitris Papastamos
2011-05-02 12:28 ` [PATCH 2/2 v2] ASoC: soc-cache: cache a pointer to the last accessed rbtree block Dimitris Papastamos
2011-05-02 14:29 ` [PATCH 1/2 v2] ASoC: soc-cache: block based rbtree compression Takashi Iwai
2011-05-02 14:40 ` Dimitris Papastamos
2011-05-02 14:46 ` Takashi Iwai
2011-05-02 14:51 ` Dimitris Papastamos
2011-05-02 14:42 ` Dimitris Papastamos
2011-05-02 14:47 ` Takashi Iwai
2011-05-02 14:58 ` Dimitris Papastamos
2011-05-03 9:43 ` Mark Brown
2011-05-03 10:38 ` Takashi Iwai
2011-05-03 10:47 ` Mark Brown
2011-05-03 10:50 ` Takashi Iwai
2011-05-03 11:02 ` Mark Brown
2011-05-03 12:25 ` Takashi Iwai
2011-05-03 13:02 ` Mark Brown
2011-05-03 13:18 ` Takashi Iwai
2011-05-03 13:24 ` Mark Brown
2011-05-03 13:32 ` Takashi Iwai
2011-05-03 13:51 ` Mark Brown
2011-05-03 14:07 ` Takashi Iwai
2011-05-03 14:27 ` Mark Brown
2011-05-03 15:22 ` Takashi Iwai
2011-05-03 15:24 ` Mark Brown
2011-05-03 15:30 ` Takashi Iwai
2011-05-03 15:40 ` Mark Brown
2011-05-03 15:47 ` Takashi Iwai
2011-05-03 15:48 ` Mark Brown
2011-05-03 15:54 ` Takashi Iwai
2011-05-03 15:55 ` Mark Brown
2011-05-03 16:06 ` Takashi Iwai
2011-05-03 11:21 ` Mark Brown
2011-05-03 11:24 ` Dimitris Papastamos
2011-05-03 11:26 ` Mark Brown
2011-05-03 11:46 ` Dimitris Papastamos
2011-05-03 13:44 ` Mark Brown [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=20110503134427.GN1762@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=dp@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
--cc=lrg@ti.com \
--cc=patches@opensource.wolfsonmicro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.