From: David Howells <dhowells@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: dhowells@redhat.com, Chris Mason <chris.mason@oracle.com>,
balajirrao@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] BTRFS: Transpose parent_objectid and parent_gen in struct btrfs_fid
Date: Wed, 18 Mar 2009 17:38:35 +0000 [thread overview]
Message-ID: <30514.1237397915@redhat.com> (raw)
In-Reply-To: <1237396909.27829.102.camel@macbook.infradead.org>
David Woodhouse <dwmw2@infradead.org> wrote:
> But this struct is packed anyway -- we're not changing much on the wire;
> it's just a case of how efficient it is to load that single uint64_t
> from an unaligned location. Is that _really_ something we're ever going
> to notice?
If the CPU doing the load/store throws a misalignment exception or just
ignores the instruction because it's misaligned, it might make for interesting
debugging.
David
next prev parent reply other threads:[~2009-03-18 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 16:16 [PATCH] BTRFS: Transpose parent_objectid and parent_gen in struct btrfs_fid David Howells
2009-03-18 17:00 ` Chris Mason
2009-03-18 17:05 ` David Howells
2009-03-18 17:21 ` David Woodhouse
2009-03-18 17:38 ` David Howells [this message]
2009-03-18 17:46 ` David Woodhouse
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=30514.1237397915@redhat.com \
--to=dhowells@redhat.com \
--cc=balajirrao@gmail.com \
--cc=chris.mason@oracle.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.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