From: Benjamin LaHaise <bcrl@kvack.org>
To: Octavian Purdila <octavian.purdila@intel.com>
Cc: Zach Brown <zab@redhat.com>,
Kent Overstreet <koverstreet@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-aio@kvack.org,
linux-s390@vger.kernel.org, schwidefsky@de.ibm.com,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH v3 next/akpm] aio: convert the ioctx list to radix tree
Date: Tue, 18 Jun 2013 15:08:17 -0400 [thread overview]
Message-ID: <20130618190817.GC16399@kvack.org> (raw)
In-Reply-To: <CAE1zotLsK47ni8-Dky6fyqZmeN3zGqKvcne9HDQbUwDi4Cia_Q@mail.gmail.com>
On Tue, Jun 18, 2013 at 10:05:22PM +0300, Octavian Purdila wrote:
> On Fri, Jun 14, 2013 at 5:20 PM, Octavian Purdila
> <octavian.purdila@intel.com> wrote:
> > I picked up Ben's patch and incorporated Zach's idea and the first
> > results look promising, as expected. I am going to do a full test with
> > the same workload I've used for rbtree and come back with the results
> > and the patch in a day or so.
> >
>
> Unfortunately, I still see performance degradation for the one ioctx
> case even when using IDR. I am using the same fio benchmark as before.
How much of a regression?
-ben
--
"Thought is the essence of where you are now."
next prev parent reply other threads:[~2013-06-18 19:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 11:40 [PATCH v3 next/akpm] aio: convert the ioctx list to radix tree Octavian Purdila
2013-05-10 20:40 ` Andrew Morton
2013-05-10 21:15 ` Kent Overstreet
2013-05-13 21:01 ` Octavian Purdila
2013-06-12 18:14 ` Kent Overstreet
2013-06-12 18:24 ` Benjamin LaHaise
2013-06-12 19:40 ` Zach Brown
2013-06-14 14:20 ` Octavian Purdila
2013-06-18 19:05 ` Octavian Purdila
2013-06-18 19:08 ` Benjamin LaHaise [this message]
2013-06-18 19:32 ` Octavian Purdila
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=20130618190817.GC16399@kvack.org \
--to=bcrl@kvack.org \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=koverstreet@google.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=octavian.purdila@intel.com \
--cc=schwidefsky@de.ibm.com \
--cc=zab@redhat.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.