From: David Howells <dhowells@redhat.com>
To: "Josh Boyer" <jwboyer@gmail.com>
Cc: "David Howells" <dhowells@redhat.com>,
torvalds@osdl.org, akpm@osdl.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org#
Subject: Re: [PATCH 0/4] Use 64-bit inode numbers internally in the kernel
Date: Tue, 15 Aug 2006 09:21:53 +0100 [thread overview]
Message-ID: <7329.1155630113@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <625fc13d0608141736q50dea86dh94cdf4ef19fe56d9@mail.gmail.com>
Josh Boyer <jwboyer@gmail.com> wrote:
> Out of curiosity, is there a performance hit for 32-bit systems? Have
> you done any minimal benchmarks to see?
Yes, I'm sure there is, but we're talking performance vs correctness.
David
next prev parent reply other threads:[~2006-08-15 8:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 21:15 [PATCH 0/4] Use 64-bit inode numbers internally in the kernel David Howells
2006-08-14 21:15 ` [RHEL5 PATCH 1/4] Provide fallback full 64-bit divide/modulus ops for gcc David Howells
2006-08-15 6:44 ` Jan Engelhardt
2006-08-15 8:10 ` Andi Kleen
2006-08-15 8:29 ` David Howells
2006-08-18 8:39 ` Pavel Machek
2006-08-18 10:33 ` David Howells
2006-08-14 21:15 ` [RHEL5 PATCH 2/4] VFS: Make inode numbers 64-bits David Howells
2006-08-15 1:31 ` Al Viro
2006-08-15 8:21 ` David Howells
2006-08-15 9:06 ` Al Viro
2006-08-15 8:32 ` David Howells
2006-08-15 9:02 ` Al Viro
2006-08-15 9:25 ` David Howells
2006-08-15 12:45 ` Stephen Rothwell
2006-08-15 6:48 ` Jan Engelhardt
2006-08-14 21:15 ` [RHEL5 PATCH 3/4] VFS: Clear up u-long-long ino_t print format warnings David Howells
2006-08-14 21:15 ` [RHEL5 PATCH 4/4] VFS: Fix 64-bit ino_t warning in CacheFiles facility David Howells
2006-08-15 0:36 ` [PATCH 0/4] Use 64-bit inode numbers internally in the kernel Josh Boyer
2006-08-15 8:21 ` David Howells [this message]
2006-08-15 9:13 ` Al Viro
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=7329.1155630113@warthog.cambridge.redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@osdl.org \
--cc=jwboyer@gmail.com \
--cc=linux-fsdevel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox