Re: How to map high memory for block io
- From: Pierre Ossman <drzeus-list@xxxxxxxxx>
- Date: Thu, 02 Mar 2006 08:26:50 +0100
Russell King wrote:
On Tue, Jan 31, 2006 at 07:39:02PM +0100, Pierre Ossman wrote:
Jens Axboe wrote:
On Mon, Jan 30 2006, Pierre Ossman wrote:Russell, what's your view on this? And how should we handle it with
Jens Axboe wrote:Disabling clustering is by far the least expensive way to accomplish it.
Ah, you need to disable clustering to prevent that from happening! I wasAnd which is the lesser evil, highmem bounce buffers or disabling
confused there for a while.
clustering? I'd probably vote for the former since the MMC overhead can
be quite large.
regard to MMC drivers?
Okay, I've hit this same problem (but in a slightly different way) with
mmci.c. The way I'm proposing to fix this for mmci is to introduce a
new capability which says "clustering is supported by this driver."
This will decrease performance more than necessary for drivers that can
do clustering, just not in highmem. So what about another flag that says
"highmem is supported by this driver"?
Rgds
Pierre
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: How to map high memory for block io
- From: Russell King
- Re: How to map high memory for block io
- References:
- Re: How to map high memory for block io
- From: Russell King
- Re: How to map high memory for block io
- Prev by Date: Re: FUA and 311x (was Re: LibPATA code issues / 2.6.15.4)
- Next by Date: Re: [ANNOUNCE] LiSt - Linux Statistics - www.linux-stats.org
- Previous by thread: Re: How to map high memory for block io
- Next by thread: Re: How to map high memory for block io
- Index(es):
Relevant Pages
|