From: David Mosberger <davidm@napali.hpl.hp.com>
To: Jack Steiner <steiner@sgi.com>
Cc: davidm@hpl.hp.com, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] - Reduce TLB flushing during process migration
Date: Wed, 7 Jul 2004 11:30:01 -0700 [thread overview]
Message-ID: <16620.16681.811228.597631@napali.hpl.hp.com> (raw)
In-Reply-To: <20040707154800.GA17818@sgi.com>
>>>>> On Wed, 7 Jul 2004 10:48:00 -0500, Jack Steiner <steiner@sgi.com> said:
Jack> As far as the tlb_migrate patch is concerned, the change to
Jack> the way machvec noop functions are implemented is mostly
Jack> unrelated to the tlb_migrate patch. We can apply the patches
Jack> in 2 ways:
Jack> - change machvec noop functions
Jack> - rework the tlb_migrate patch on top of that change
Jack> OR
Jack> - apply the tlb_migrate patch in it's current form
Jack> - change the machvec noop functions including the tlb_migrate noop
Jack> Either works. I'm partial to #2 (easier) but will do either....
I'd be ok with #2 except that if we do it that way, I bet that we'll
forget about changing the machvec noop functions... ;-)
Jack> Note: calling a noop function after an explicit process
Jack> migration is untidy but is not a measurable performance
Jack> problem. I agree, however, that the noop function should be
Jack> improved. At some point in the future, other noop functions
Jack> may be added that ARE performance sensitive. It is good to
Jack> have the correct infrastructure implemented.
Precisely.
--david
prev parent reply other threads:[~2004-07-07 18:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 14:38 Jack Steiner
2004-06-23 21:33 ` Andrew Morton
2004-06-24 12:55 ` Jack Steiner
2004-06-24 18:44 ` Andrew Morton
2004-06-25 14:23 ` Jack Steiner
2004-06-26 5:10 ` David Mosberger
2004-07-02 17:39 ` Jack Steiner
2004-07-07 0:01 ` David Mosberger
2004-07-07 13:52 ` John Richard Moser
2004-07-07 15:48 ` Jack Steiner
2004-07-07 18:30 ` David Mosberger [this message]
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=16620.16681.811228.597631@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=akpm@osdl.org \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.com \
/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
all inboxes | Powered by JetHome®