mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Horst von Brand <vonbrand@sleipnir.valparaiso.cl>,
	Andrea Arcangeli <andrea@suse.de>,
	ehrhardt@mathematik.uni-ulm.de, linux-kernel@vger.kernel.org
Subject: Re: VM-related Oops: 2.4.15pre1
Date: Sun, 18 Nov 2001 20:22:52 -0700	[thread overview]
Message-ID: <20011118202252.A8708@vger.timpanogas.org> (raw)
In-Reply-To: <200111181710.fAIHAlCF011794@sleipnir.valparaiso.cl> <Pine.LNX.4.33.0111181803040.7482-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0111181803040.7482-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Sun, Nov 18, 2001 at 06:04:16PM -0800

On Sun, Nov 18, 2001 at 06:04:16PM -0800, Linus Torvalds wrote:
> 
> On Sun, 18 Nov 2001, Horst von Brand wrote:
> > Linus Torvalds <torvalds@transmeta.com> said:
> > > And nope, not really. It does use plain stores to page->flags, and I agree
> > > that it is ugly, but if the page was locked before calling it, all the
> > > stores will be with the PG_lock bit set - and even plain stores _are_
> > > documented to be atomic on x86 (and on all other reasonable architectures
> > > too).
> >
> > Even unaligned stores?
> 
> Actually, even unaligned stores (which page->flags is NOT) are atomic,
> even if Intel strongly discourages them (for performance reasons if no
> others) and there tends to be documentation that doesn't guarantee it.
> 
> 		Linus
> 

This is true.  They Generate what's called a "split lock" bus transaction
where the bus will hold LOCK# low across the several clock cycles to 
complete the write.  They are **VERY** heavy, BTW, and really cause 
nasty performance hits.

Jeff




> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2001-11-19  2:21 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-16 22:23 Simon Kirby
2001-11-17 22:53 ` Christian Ehrhardt
2001-11-18  3:12 ` Linus Torvalds
2001-11-18  4:10   ` Andrea Arcangeli
2001-11-18  6:24     ` Linus Torvalds
2001-11-18  6:37       ` Andrea Arcangeli
2001-11-18  7:31         ` Linus Torvalds
2001-11-18 12:05           ` Alan Cox
2001-11-19  2:02             ` Linus Torvalds
2001-11-19  2:27               ` Linus Torvalds
2001-11-19 18:40                 ` kuznet
2001-11-19 10:15               ` Alan Cox
2001-11-19 16:39                 ` Linus Torvalds
2001-11-19 18:03                   ` Eric W. Biederman
2001-11-19 19:04                     ` Linus Torvalds
2001-11-19 23:52                   ` John Alvord
2001-11-21  2:31               ` Pavel Machek
     [not found]         ` <200111180731.fAI7VFa01371@penguin.transmeta.com>
2001-11-18  7:51           ` Andrea Arcangeli
2001-11-18 17:10       ` Horst von Brand
2001-11-19  2:04         ` Linus Torvalds
2001-11-19  3:22           ` Jeff V. Merkey [this message]
2001-11-19  8:44           ` David Woodhouse
2001-11-19 16:57             ` Linus Torvalds
2001-11-19 17:56               ` Simon Kirby
2001-11-19 18:03                 ` Linus Torvalds
2001-11-19 18:31                   ` Simon Kirby
2001-11-19 20:01                   ` Marcelo Tosatti
2001-11-19 21:26                     ` Linus Torvalds
2001-11-19 21:49                       ` Rik van Riel
2001-11-19 22:40                         ` Linus Torvalds
2001-11-19 22:59                           ` Rik van Riel
2001-11-19 23:03                             ` Linus Torvalds
2001-11-20  0:06                               ` Rik van Riel
2001-11-20  0:08                                 ` Linus Torvalds
2001-11-20  0:27                                   ` Rik van Riel
2001-11-19 23:27                   ` Simon Kirby
2001-11-19 23:38                     ` Linus Torvalds
2001-11-19 23:52                       ` Simon Kirby

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=20011118202252.A8708@vger.timpanogas.org \
    --to=jmerkey@vger.timpanogas.org \
    --cc=andrea@suse.de \
    --cc=ehrhardt@mathematik.uni-ulm.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=vonbrand@sleipnir.valparaiso.cl \
    /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®