From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
"Randy.Dunlap" <rddunlap@osdl.org>,
William Lee Irwin III <wli@holomorphy.com>,
Jens Axboe <axboe@suse.de>, Andrew Morton <akpm@osdl.org>
Subject: Re: news about IDE PIO HIGHMEM bug (was: Re: 2.6.9-mm1)
Date: Wed, 27 Oct 2004 10:36:48 -0700 [thread overview]
Message-ID: <30640000.1098898608@flay> (raw)
In-Reply-To: <417FC5CB.9040204@pobox.com>
> Unfortunately, it's not.
>
> The block layer just tells us "it's a contiguous run of memory", which implies nothing really about the allocation size.
>
> Bart and I (and others?) essentially need a "page+1" thing (for 2.4.x too!), that won't break in the face of NUMA/etc.
>
> Alternatively (or additionally), we may need to make sure the block layer doesn't merge across zones or NUMA boundaries or whatnot.
The latter would be rather more efficient. I don't know how often you
end up doing each operation though ... the page+1 vs the attemtped merge.
Depends on the ratio, I guess.
M.
WARNING: multiple messages have this Message-ID (diff)
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
"Randy.Dunlap" <rddunlap@osdl.org>,
William Lee Irwin III <wli@holomorphy.com>,
Jens Axboe <axboe@suse.de>, Andrew Morton <akpm@osdl.org>
Subject: Re: news about IDE PIO HIGHMEM bug (was: Re: 2.6.9-mm1)
Date: Wed, 27 Oct 2004 10:36:48 -0700 [thread overview]
Message-ID: <30640000.1098898608@flay> (raw)
In-Reply-To: <417FC5CB.9040204@pobox.com>
> Unfortunately, it's not.
>
> The block layer just tells us "it's a contiguous run of memory", which implies nothing really about the allocation size.
>
> Bart and I (and others?) essentially need a "page+1" thing (for 2.4.x too!), that won't break in the face of NUMA/etc.
>
> Alternatively (or additionally), we may need to make sure the block layer doesn't merge across zones or NUMA boundaries or whatnot.
The latter would be rather more efficient. I don't know how often you
end up doing each operation though ... the page+1 vs the attemtped merge.
Depends on the ratio, I guess.
M.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-10-27 17:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <58cb370e041027074676750027@mail.gmail.com>
2004-10-27 15:14 ` news about IDE PIO HIGHMEM bug (was: Re: 2.6.9-mm1) Jeff Garzik
2004-10-27 15:14 ` Jeff Garzik
2004-10-27 15:52 ` Martin J. Bligh
2004-10-27 15:52 ` Martin J. Bligh
2004-10-27 15:59 ` Jeff Garzik
2004-10-27 15:59 ` Jeff Garzik
2004-10-27 17:36 ` Martin J. Bligh [this message]
2004-10-27 17:36 ` Martin J. Bligh
2004-10-27 16:01 ` Martin J. Bligh
2004-10-27 16:01 ` Martin J. Bligh
2004-10-27 16:35 ` [PATCH] " Jeff Garzik
2004-10-27 21:29 ` Andrew Morton
2004-10-27 21:29 ` Andrew Morton
2004-10-27 21:31 ` Jeff Garzik
2004-10-27 21:31 ` Jeff Garzik
2004-10-27 21:34 ` William Lee Irwin III
2004-10-27 21:34 ` William Lee Irwin III
2004-10-27 18:08 ` Christoph Hellwig
2004-10-27 18:08 ` Christoph Hellwig
2004-10-27 18:33 ` news about IDE PIO HIGHMEM bug Jeff Garzik
2004-10-27 18:33 ` Jeff Garzik
2004-10-27 18:48 ` William Lee Irwin III
2004-10-27 18:48 ` William Lee Irwin III
2004-10-28 0:18 ` William Lee Irwin III
2004-10-28 0:18 ` William Lee Irwin III
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=30640000.1098898608@flay \
--to=mbligh@aracnet.com \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=bzolnier@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rddunlap@osdl.org \
--cc=wli@holomorphy.com \
/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.