From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: speeding up thread-creation
Date: Fri, 21 Nov 2003 08:19:59 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106940282522654@msgid-missing> (raw)
It occurred to me that at present, we're copying lots of state on a
clone2() for absolutely no reason. Not only that, but the large size
of the "thread_struct" probably also causes poor cache-locality since
the task-structure is effectively split in two, with a large unused
gap in between. I think it might make sense to move all the large
thread_struct-state (IA-32 registers, pmcs[], pmds[], dbr[], ibr[],
and fph[]) into a separate "thread_lazy" structure and then put that
structure at a place where it doesn't hurt (perhaps above the
thread_info structure). If I counted right, this state accounts for
2KB so not copying it in copy_process() ought to speed up
thread-creation significantly and avoid stomping needlessly on the L1
d-cache.
Anyone interested in playing with this idea?
--david
next reply other threads:[~2003-11-21 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-21 8:19 David Mosberger [this message]
2003-11-21 17:22 ` speeding up thread-creation Stephane Eranian
2003-11-21 18:31 ` David Mosberger
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=marc-linux-ia64-106940282522654@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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 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.