From: Andrew Morton <akpm@osdl.org>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-kernel@vger.kernel.org, viro@parcelfarce.linux.theplanet.co.uk
Subject: Re: [PATCH] unified device list allocator
Date: Mon, 7 Mar 2005 21:33:02 -0800 [thread overview]
Message-ID: <20050307213302.560de053.akpm@osdl.org> (raw)
In-Reply-To: <20050308051818.GI3120@waste.org>
Matt Mackall <mpm@selenic.com> wrote:
>
> + /* search for insertion point in reverse for dynamic allocation */
> + list_for_each_prev(l, list) {
hrmph. Any time we do anything in O(n) time, some smarty comes along with
a workload which blows us out of the water. Although it's hard to think of
any register_blkdev()-intensive workloads.
It's not possible to do this with prio-trees?
next prev parent reply other threads:[~2005-03-08 5:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 5:18 [PATCH] unified device list allocator Matt Mackall
2005-03-08 5:33 ` Andrew Morton [this message]
2005-03-08 5:43 ` Christoph Hellwig
2005-03-08 5:50 ` Andrew Morton
2005-03-08 5:56 ` Christoph Hellwig
2005-03-08 6:11 ` Matt Mackall
2005-03-08 6:31 ` Christoph Hellwig
2005-03-08 6:35 ` Matt Mackall
2005-03-08 6:01 ` Matt Mackall
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=20050307213302.560de053.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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