From: "George Spelvin" <linux@horizon.com>
To: hughd@google.com, linux@horizon.com
Cc: herbert@gondor.hengli.com.au, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mpm@selenic.com, penberg@cs.helsinki.fi
Subject: Re: [PATCH 1/8] drivers/random: Cache align ip_random better
Date: 16 Mar 2011 14:10:23 -0400 [thread overview]
Message-ID: <20110316181023.2090.qmail@science.horizon.com> (raw)
In-Reply-To: <alpine.LSU.2.00.1103161011370.13407@sister.anvils>
> I'm intrigued: please educate me. On what architectures does cache-
> aligning a 48-byte buffer (previously offset by 4 bytes) speed up
> copying from it, and why? Does the copying involve 8-byte or 16-byte
> instructions that benefit from that alignment, rather than cacheline
> alignment?
I had two thoughts in my head when I wrote that:
1) A smart compiler could note the alignment and issue wider copy
instructions. (Especially on alignment-required architectures.)
2) The cacheline fetch would get more data faster. The data would
be transferred in the first 6 beats of the load from RAM (assuming a
64-bit data bus) rather than waiting for 7, so you'd finish the copy
1 ns sooner or so. Similar 1-cycle win on a 128-bit Ln->L(n-1) cache
transfer.
As I said, "infinitesimal". The main reason that I bothered to
generate a patch was that it appealed to my sense of neatness to
keep the 3x16-byte buffer 16-byte aligned.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-03-16 18:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 0:20 [PATCH 1/8] drivers/random: Cache align ip_random better George Spelvin
2011-03-16 2:54 ` Matt Mackall
2011-03-16 6:24 ` Pekka Enberg
2011-03-16 17:17 ` Hugh Dickins
2011-03-16 18:10 ` George Spelvin [this message]
2011-03-16 18:42 ` Hugh Dickins
2011-03-16 19:45 ` George Spelvin
2011-03-22 9:03 ` Herbert Xu
2011-03-16 18:23 ` Matt Mackall
2011-03-16 19:26 ` Eric Dumazet
2011-03-16 19:55 ` Matt Mackall
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=20110316181023.2090.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=herbert@gondor.hengli.com.au \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=penberg@cs.helsinki.fi \
/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;
as well as URLs for NNTP newsgroup(s).