From: Matthew Frost <artusemrys@sbcglobal.net>
To: Andrew Morton <akpm@osdl.org>
Cc: vgoyal@in.ibm.com, galak@kernel.crashing.org,
linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: [RFC][PATCH 1/6] kconfigurable resources core changes
Date: Thu, 18 May 2006 01:14:08 -0500 [thread overview]
Message-ID: <446C10B0.6060602@sbcglobal.net> (raw)
In-Reply-To: <20060517224334.7d2bb5eb.akpm@osdl.org>
Andrew Morton wrote:
> Matthew Frost <artusemrys@sbcglobal.net> wrote:
>> This may sound like a dumb question, but aside from code bloat, what are
>> the performance issues involved in running 64-bit resources on 32-bit
>> systems?
>
> Unmeasurably minor, I expect.
Noted, with thanks.
>
> No sane software project would take on this (small) maintenance burden just
> to save 50-60 kbytes. We would though.
I'm aware of that, and I'm not complaining. :) It's one of the things
I love about this project. It's a healthy insanity, enforced by the
squeaking of the wheels. Besides, code bloat is cumulative.
Matt
prev parent reply other threads:[~2006-05-18 6:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 17:28 [RFC][PATCH 1/6] kconfigurable resources core changes Vivek Goyal
2006-05-05 17:30 ` [RFC][PATCH 2/6] kconfigurable resources driver pci changes Vivek Goyal
2006-05-05 17:31 ` [RFC][PATCH 3/6] kconfigurable resources driver others changes Vivek Goyal
2006-05-05 17:33 ` [RFC][PATCH 4/6] kconfigurable resources arch dependent changes (arch/[a-i]*) Vivek Goyal
2006-05-05 17:34 ` [RFC][PATCH 5/6] kconfigurable resources arch dependent changes (arch/[j-p]*) Vivek Goyal
2006-05-05 17:36 ` [RFC][PATCH 6/6] kconfigurable resources arch dependent changes (arch/[q-z]*) Vivek Goyal
2006-05-05 18:10 ` [RFC][PATCH 1/6] kconfigurable resources core changes Greg KH
2006-05-05 18:35 ` Vivek Goyal
2006-05-09 19:33 ` Kumar Gala
2006-05-09 20:03 ` Vivek Goyal
2006-05-18 5:19 ` Matthew Frost
2006-05-18 5:43 ` Andrew Morton
2006-05-18 6:14 ` Matthew Frost [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=446C10B0.6060602@sbcglobal.net \
--to=artusemrys@sbcglobal.net \
--cc=akpm@osdl.org \
--cc=galak@kernel.crashing.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@in.ibm.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.