[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47A78797.8060601@linux.intel.com>
Date: Mon, 04 Feb 2008 13:45:59 -0800
From: Arjan van de Ven <arjan@...ux.intel.com>
To: Jens Axboe <jens.axboe@...cle.com>
CC: Zach Brown <zach.brown@...cle.com>, David Chinner <dgc@....com>,
Nick Piggin <npiggin@...e.de>,
"Siddha, Suresh B" <suresh.b.siddha@...el.com>,
linux-kernel@...r.kernel.org, mingo@...e.hu, ak@...e.de,
James.Bottomley@...elEye.com, andrea@...e.de, clameter@....com,
akpm@...ux-foundation.org, andrew.vasquez@...gic.com,
willy@...ux.intel.com
Subject: Re: [rfc] direct IO submission and completion scalability issues
Jens Axboe wrote:
>> I was imagining the patch a little bit differently (per-cpu tasks, do a
>> wake_up from the driver instead of cpu nr testing up in blk, work
>> queues, whatever), but we know how to iron out these kinds of details ;).
>
> per-cpu tasks/wq's might be better, it's a little awkward to jump
> through hoops
>
one caveat btw; when the multiqueue storage hw becomes available for Linux,
we need to figure out how to deal with the preference thing; since there
honoring a "non-logical" preference would be quite expensive (it means
you can't make the local submit queues lockless etc etc), so before we go down
the road of having widespread APIs for this stuff.. we need to make sure we're
not going to do something that's going to be really stupid 6 to 18 months down the road.
--
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