From: Eric Sandeen <sandeen@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] don't special-case 32MB machines
Date: Thu, 08 Feb 2007 14:38:57 -0600 [thread overview]
Message-ID: <45CB8A61.6060902@redhat.com> (raw)
In-Reply-To: <20070208192712.GA1461@infradead.org>
Christoph Hellwig wrote:
> On Wed, Feb 07, 2007 at 07:31:39PM -0600, Eric Sandeen wrote:
>> This one may be a bit silly, but:
>>
>> All the special cases for 32MB machines probably aren't so useful anymore...
>>
>> Or maybe this points to the need to bump up the scaling points & sizes a
>> bit?
>>
>> Also remove duplicate, unused XFS_MAX_RW_NBMAPS definitions in linux
>> subdirs.
>
> Sounds good. Any chance you could kill off xfs_physmem completely?
>
Hm, why out of curiosity? Because you think xfs should never be looking
at system memory, or because you don't like the name, or ...?
-Eric
prev parent reply other threads:[~2007-02-08 20:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 1:31 [PATCH] don't special-case 32MB machines Eric Sandeen
2007-02-08 19:27 ` Christoph Hellwig
2007-02-08 20:38 ` Eric Sandeen [this message]
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=45CB8A61.6060902@redhat.com \
--to=sandeen@redhat.com \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox