mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: David Howells <dhowells@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	torvalds@osdl.org, akpm@osdl.org, davidm@snapgear.com,
	linux-kernel@vger.kernel.org, uclinux-dev@uclinux.org
Subject: Re: [PATCH] VM routine fixes
Date: Tue, 9 Nov 2004 14:01:22 +0000	[thread overview]
Message-ID: <20041109140122.GA5388@infradead.org> (raw)
In-Reply-To: <15068.1100008386@redhat.com>

On Tue, Nov 09, 2004 at 01:53:06PM +0000, David Howells wrote:
> 
> > Please don't stick CONFIG_MMU all over the place but keep them in as small
> > as possible blocks.
> 
> You seem to have changed your mind. Last I heard from you wanted them in as
> few large blocks as possible. Now you want them in many small blocks. If you
> want it changing, please feel free to supply me with a patch.

sorry, typo.  Should have read as large as possible - small doesn't make
sense with the first half of the sentence anyway.

> > As I told you before please move registration of MMU-only sysctls
> > to a MMU-only file in mm/
> 
> No. These belong in the vm_table. It doesn't seem especially straightforward
> to do what you want. If you want it doing your way, then feel free to send
> Andrew a patch.

It is.  You can register multiple tables for the same hierachy.

> > this is nasty.  The right thing would probably to swich !MMU arches
> > to use the compount-page mechanism from the hugetlb code for this.
> 
> Supply me with a patch and I'll test it. I don't know how the compound-page
> stuff works, but it's quite possibly the wrong way to do it. There is no MMU
> available, so you can't generate adjacency that way.

so look at the code.  It's not about the MMU at all, it's about handling
the Linux page structures.   What you're doing is a big mess and should
not be merged.  So if you want to fix the issue do it properly.


  reply	other threads:[~2004-11-09 14:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08 14:32 dhowells
2004-11-09 12:55 ` Christoph Hellwig
2004-11-09 13:53 ` David Howells
2004-11-09 14:01   ` Christoph Hellwig [this message]
2004-11-10 13:37   ` David Howells
2004-11-10 19:01     ` Andrew Morton
2004-11-11  1:17       ` David Woodhouse
2004-11-11  2:26         ` Andrew Morton
2004-11-11 11:29         ` David Howells
2004-11-11 11:43           ` Andrew Morton
2004-11-11 12:03           ` David Howells
2004-11-11 22:31 ` Andrew Morton
2004-11-12 10:33 ` David Howells
2004-11-12 10:38   ` Andrew Morton
2004-11-12 11:05   ` David Howells
2004-11-14  5:07     ` Linus Torvalds
2004-11-15 13:14     ` David Howells
2004-11-15 15:35       ` Linus Torvalds

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=20041109140122.GA5388@infradead.org \
    --to=hch@infradead.org \
    --cc=akpm@osdl.org \
    --cc=davidm@snapgear.com \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=uclinux-dev@uclinux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome