From: david mosberger <dmosberger@gmail.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] delete sync.i in ia64_switch_to()
Date: Wed, 07 Sep 2005 17:59:45 +0000 [thread overview]
Message-ID: <ed5aea4305090710595313fd96@mail.gmail.com> (raw)
In-Reply-To: <200509070723.j877N9g25144@unix-os.sc.intel.com>
On 9/7/05, Jim Hull <jim.hull@hp.com> wrote:
> That sync.i is not old code - it is required.
Yes, the sync.i was added by Asit at some point precisely for the
reasons you explained. I believe we concluded at the time that the
"mf" wasn't needed since we'd be guaranteed to have a fence in the
execution-path anyhow (IIRC, it was due to locks being
acquired/released on the paths in question). I'm not sure, however,
whether this point has been considered when kernel-preemption support
was added. The folks caring about CONFIG_PREEMPT may want to
reconsider that issue if not.
--david
next prev parent reply other threads:[~2005-09-07 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 7:22 [patch] delete sync.i in ia64_switch_to() Chen, Kenneth W
2005-09-07 8:00 ` Chen, Kenneth W
2005-09-07 17:33 ` Jim Hull
2005-09-07 17:59 ` david mosberger [this message]
2005-09-07 19:12 ` Chen, Kenneth W
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=ed5aea4305090710595313fd96@mail.gmail.com \
--to=dmosberger@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox