From: Luca Barbieri <ldb@ldb.ods.org>
To: Linux-Kernel ML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>
Subject: [PATCH] [2.5 i386] Swap TLS and TSS entries to improve spatial locality
Date: 07 Aug 2002 19:05:38 +0200 [thread overview]
Message-ID: <1028739938.11775.30.camel@ldb> (raw)
[-- Attachment #1: Type: text/plain, Size: 2185 bytes --]
GDT entries are usually accessed with this pattern:
* Interrupt: read TSS (for ss0:esp0) and kernel CS/DS
* Schedule: write TLS, LDT, load FS and GS (either TLS, user DS
or LDT entry)
* Return: read user CS/DS
Swapping the TLS and TSS entries causes the GDT entries that are read
during interrupt and schedule to be in the same cacheline.
diff --exclude-from=/home/ldb/src/linux-exclude -urNd a/arch/i386/kernel/head.S b/arch/i386/kernel/head.S
--- a/arch/i386/kernel/head.S 2002-07-29 04:18:06.000000000 +0200
+++ b/arch/i386/kernel/head.S 2002-08-07 19:03:24.000000000 +0200
@@ -416,12 +416,12 @@
*/
ENTRY(cpu_gdt_table)
.quad 0x0000000000000000 /* NULL descriptor */
- .quad 0x0000000000000000 /* TLS descriptor */
+ .quad 0x0000000000000000 /* TSS descriptor */
.quad 0x00cf9a000000ffff /* 0x10 kernel 4GB code at 0x00000000 */
.quad 0x00cf92000000ffff /* 0x18 kernel 4GB data at 0x00000000 */
.quad 0x00cffa000000ffff /* 0x23 user 4GB code at 0x00000000 */
.quad 0x00cff2000000ffff /* 0x2b user 4GB data at 0x00000000 */
- .quad 0x0000000000000000 /* TSS descriptor */
+ .quad 0x0000000000000000 /* TLS descriptor */
.quad 0x0000000000000000 /* LDT descriptor */
/*
* The APM segments have byte granularity and their bases
diff --exclude-from=/home/ldb/src/linux-exclude -urNd a/include/asm-i386/desc.h b/include/asm-i386/desc.h
--- a/include/asm-i386/desc.h 2002-08-02 01:19:14.000000000 +0200
+++ b/include/asm-i386/desc.h 2002-08-07 18:56:12.000000000 +0200
@@ -7,12 +7,12 @@
* The layout of the per-CPU GDT under Linux:
*
* 0 - null
- * 1 - Thread-Local Storage (TLS) segment
+ * 1 - TSS
* 2 - kernel code segment
* 3 - kernel data segment
* 4 - user code segment <==== new cacheline
* 5 - user data segment
- * 6 - TSS
+ * 6 - Thread-Local Storage (TLS) segment
* 7 - LDT
* 8 - APM BIOS support <==== new cacheline
* 9 - APM BIOS support
@@ -27,8 +27,8 @@
* 18 - not used
* 19 - not used
*/
-#define TLS_ENTRY 1
-#define TSS_ENTRY 6
+#define TSS_ENTRY 1
+#define TLS_ENTRY 6
#define LDT_ENTRY 7
/*
* The interrupt descriptor table has room for 256 idt's,
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2002-08-07 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 17:05 Luca Barbieri [this message]
2002-08-07 17:07 ` [PATCH] [2.5 i386] Swap TLS and TSS entries to improve spatial locality Ingo Molnar
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=1028739938.11775.30.camel@ldb \
--to=ldb@ldb.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.