From: David Woodhouse <dwmw2@infradead.org>
To: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
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: Mon, 19 Nov 2001 08:44:28 +0000 [thread overview]
Message-ID: <588.1006159468@redhat.com> (raw)
In-Reply-To: <20011118202252.A8708@vger.timpanogas.org>
In-Reply-To: <20011118202252.A8708@vger.timpanogas.org> <200111181710.fAIHAlCF011794@sleipnir.valparaiso.cl> <Pine.LNX.4.33.0111181803040.7482-100000@penguin.transmeta.com>
jmerkey@vger.timpanogas.org said:
> 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.
Is it worth making put_unaligned and get_unaligned on x86 avoid this by
loading/storing the two halves of the required datum separately, then?
--
dwmw2
next prev parent reply other threads:[~2001-11-19 8:46 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 22:23 VM-related Oops: 2.4.15pre1 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
2001-11-19 8:44 ` David Woodhouse [this message]
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=588.1006159468@redhat.com \
--to=dwmw2@infradead.org \
--cc=andrea@suse.de \
--cc=ehrhardt@mathematik.uni-ulm.de \
--cc=jmerkey@vger.timpanogas.org \
--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 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.