From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Jens Axboe <axboe@suse.de>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: How to map high memory for block io
Date: Fri, 27 Jan 2006 22:58:59 +0100 [thread overview]
Message-ID: <43DA97A3.4080408@drzeus.cx> (raw)
In-Reply-To: <43DA84B2.8010501@drzeus.cx>
Pierre Ossman wrote:
> Russell King wrote:
>
>> On Fri, Jan 27, 2006 at 09:22:06PM +0100, Jens Axboe wrote:
>>
>>
>>> That is definitely valid, same goes for the bio_vec structure. They map
>>> _a_ page, after all :-)
>>>
>>>
>> Okay. Pierre - are you saying that you have an sg entry where
>> sg->offset + sg->length > PAGE_SIZE, and hence is causing you to
>> cross a page boundary?
>>
>>
>>
>
> That, and sg->length > PAGE_SIZE. On highmem systems this causes all
> kinds of funky behaviour. Usually just bogus data in the buffers though.
>
>
Test done here, few minutes ago. Added this to the wbsd driver in its
kmap routine:
if ((host->cur_sg->offset + host->cur_sg->length) > PAGE_SIZE)
printk(KERN_DEBUG "wbsd: Big sg: %d, %d\n",
host->cur_sg->offset, host->cur_sg->length);
got:
[17385.425389] wbsd: Big sg: 0, 8192
[17385.436849] wbsd: Big sg: 0, 7168
[17385.436859] wbsd: Big sg: 0, 7168
[17385.454029] wbsd: Big sg: 2560, 5632
[17385.454216] wbsd: Big sg: 2560, 5632
And so on.
Rgds
Pierre
next prev parent reply other threads:[~2006-01-27 21:59 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 [this message]
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
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=43DA97A3.4080408@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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.