From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Pierre Ossman <drzeus-list@drzeus.cx>, Jens Axboe <axboe@suse.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: How to map high memory for block io
Date: Thu, 02 Mar 2006 11:26:13 +0100 [thread overview]
Message-ID: <4406C845.8000603@drzeus.cx> (raw)
In-Reply-To: <20060302100409.GB14017@flint.arm.linux.org.uk>
Russell King wrote:
> On Thu, Mar 02, 2006 at 10:52:04AM +0100, Pierre Ossman wrote:
>
>> Russell King wrote:
>>
>>> I think you're asking Jens that question - I know of no way to tell
>>> the block layer that clustering is fine for normal but not highmem.
>>>
>> That wasn't what I meant. What I was referring to was disabling highmem
>> altogether, the way that is done now through looking at the dma mask.
>>
>
> You need to set your struct device's dma_mask appropriately:
>
> u64 limit = BLK_BOUNCE_HIGH;
>
> if (host->dev->dma_mask && *host->dev->dma_mask)
> limit = *host->dev->dma_mask;
>
> blk_queue_bounce_limit(mq->queue, limit);
>
> Hence, if dma_mask is a NULL pointer or zero, highmem will be bounced.
>
This I know. My beef is the readability of:
if (do_dma)
*dev->dma_mask = DEVICE_DMA_MASK;
else
*dev->dma_mask = 0;
I.e. we use dma_mask even though we don't do DMA.
> Neither PNP nor your platform device sets dma_mask, so highmem will
> always be bounced in the case of wbsd - which from what you write above
> is what you require anyway.
>
>
wbsd isn't the issue, sdhci is. PCI sets a 32-bit mask by default so I
end up with highmem pages even when I'm not doing DMA.
Rgds
Pierre
next prev parent reply other threads:[~2006-03-02 10:26 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-27 6:45 How to map high memory for block io Pierre Ossman
2006-01-27 10:26 ` Jens Axboe
2006-01-27 10:33 ` Pierre Ossman
2006-01-27 10:43 ` Jens Axboe
2006-01-27 12:14 ` Pierre Ossman
2006-01-27 12:39 ` Jens Axboe
2006-01-27 13:16 ` Pierre Ossman
2006-01-27 13:48 ` Pierre Ossman
2006-01-27 14:00 ` Jens Axboe
2006-01-27 14:14 ` Pierre Ossman
2006-01-27 18:37 ` Pierre Ossman
2006-01-27 19:43 ` Russell King
2006-01-27 20:04 ` Pierre Ossman
2006-01-27 20:10 ` Jens Axboe
2006-01-27 20:14 ` Russell King
2006-01-27 20:22 ` Jens Axboe
2006-01-27 20:26 ` Russell King
2006-01-27 20:38 ` Pierre Ossman
2006-01-27 21:58 ` Pierre Ossman
2006-01-27 22:54 ` Russell King
2006-01-28 19:17 ` Jens Axboe
2006-01-28 19:32 ` Pierre Ossman
2006-01-29 15:22 ` Jens Axboe
2006-01-30 7:57 ` Pierre Ossman
2006-01-30 8:09 ` Jens Axboe
2006-01-31 18:39 ` Pierre Ossman
2006-03-01 23:29 ` Russell King
2006-03-02 7:21 ` Jens Axboe
2006-03-02 7:26 ` Pierre Ossman
2006-03-02 9:41 ` Russell King
2006-03-02 9:52 ` Pierre Ossman
2006-03-02 10:04 ` Russell King
2006-03-02 10:26 ` Pierre Ossman [this message]
2006-03-02 11:45 ` Russell King
2007-01-30 20:41 ` Pierre Ossman
2006-01-27 20:28 ` Pierre Ossman
2006-01-27 20:12 ` Pierre Ossman
2006-01-27 20:16 ` Russell King
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=4406C845.8000603@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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.