From: David Howells <dhowells@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: torvalds@osdl.org, hch@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Making compound pages mandatory
Date: Tue, 16 Nov 2004 19:41:47 +0000 [thread overview]
Message-ID: <3725.1100634107@redhat.com> (raw)
In-Reply-To: <20041116112022.67be2377.akpm@osdl.org>
> Andrea wants to do that, purely from a code coverage point of view. But it
> does add a little extra overhead.
It definitely does.
> For what reason do you propose this?
You and Christoph, amongst others, seemed dead in favour of it. Other than
that, I have no real need for it, except that it makes kobjsize() simpler.
David
next prev parent reply other threads:[~2004-11-16 19:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 18:48 [RFC] Making compound pages mandatory David Howells
2004-11-16 19:20 ` Andrew Morton
2004-11-16 19:41 ` David Howells [this message]
2004-11-17 1:50 ` Linus Torvalds
2004-11-17 2:28 ` Andrew Morton
2004-11-17 3:13 ` Nick Piggin
2004-11-17 3:22 ` Nick Piggin
2004-11-17 3:37 ` Nick Piggin
2004-11-17 3:42 ` Nick Piggin
2004-11-17 3:14 ` Linus Torvalds
2004-11-17 12:03 ` David Howells
2004-11-17 11:47 ` David Howells
2004-11-17 11:43 ` David Howells
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=3725.1100634107@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.