[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <535AD235.90604@kernel.dk>
Date: Fri, 25 Apr 2014 15:23:01 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Ming Lei <tom.leiming@...il.com>
CC: Alexander Gordeev <agordeev@...hat.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kent Overstreet <kmo@...erainc.com>,
Shaohua Li <shli@...nel.org>,
Nicholas Bellinger <nab@...ux-iscsi.org>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH RFC 0/2] percpu_ida: Take into account CPU topology when
stealing tags
On 04/25/2014 03:10 AM, Ming Lei wrote:
> Hi Jens,
>
> On Wed, Apr 23, 2014 at 9:25 AM, Jens Axboe <axboe@...nel.dk> wrote:
>> On 2014-04-22 18:53, Ming Lei wrote:
>>
>>
>>> In my null_blk test on a quad core SMP VM:
>>>
>>> - 4 hw queue
>>> - timer mode
>>>
>>> With the above approach, tag allocation from local CPU can be
>>> improved from:
>>>
>>> 5% -> 50% for boot CPU
>>> 30% -> 90% for non-boot CPU.
>>>
>>> If no one objects the idea, I'd like to post a patch for review.
>>
>>
>> Sent it out, that can't hurt. I'll take a look at it, and give it a test
>> spin as well.
>
> I have sent out the patch in below link, and appreciate much
> you will take a look at it.
>
> marc.info/?l=linux-kernel&m=139826944613225&w=2
Sorry, I did run it the other day. It has little to no effect here, but
that's mostly because there's so much other crap going on in there. The
most effective way to currently make it work better, is just to ensure
the caching pool is of a sane size.
I've got an alternative tagging scheme that I think would be useful for
the cases where the tag space to cpu ratio isn't big enough. So I think
we'll retain percpu_ida for the cases where it can cache enough, and
punt to an alternative scheme when not.
That doesn't mean we should not improve percpu_ida. There's quite a bit
of low hanging fruit in there.
--
Jens Axboe
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists