From: david mosberger <dmosberger@gmail.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 2.6.13-rc1 07/10] IOCHK interface for I/O error handling/detecting
Date: Mon, 11 Jul 2005 19:21:55 +0000 [thread overview]
Message-ID: <ed5aea4305071112212756924@mail.gmail.com> (raw)
In-Reply-To: <42CB6961.2060508@jp.fujitsu.com>
Yeah, PAL calls are very expensive. On a zx1-type machine, I/O reads
take on the order of 1,000 cycles, so a PAL call would be an order of
magnitude more expensive. Is PAL_MC_FLUSH really needed in that case?
--david
On 7/11/05, Luck, Tony <tony.luck@intel.com> wrote:
>
> >Why not be extra safe and call PAL_MC_FLUSH? Or would that be too
> >expensive?
>
> Just timed a call to PAL_MC_DRAIN (which is what I assume you meant).
>
> Just over 13,000 cycles.
>
> Is that too expensive? How long does an i/o read take from a typical device?
>
> -Tony
>
next prev parent reply other threads:[~2005-07-11 19:21 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 4:53 [PATCH 2.6.13-rc1 01/10] IOCHK interface for I/O error handling/detecting Hidetoshi Seto
2005-07-06 4:58 ` [PATCH 2.6.13-rc1 02/10] " Hidetoshi Seto
2005-07-06 5:04 ` [PATCH 2.6.13-rc1 03/10] " Hidetoshi Seto
2005-07-12 19:51 ` Linas Vepstas
2005-07-13 0:18 ` [PATCH 2.6.13-rc1 03/10] IOCHK interface for I/O error Benjamin Herrenschmidt
2005-07-13 22:42 ` [PATCH 2.6.13-rc1 03/10] IOCHK interface for I/O error handling/detecting Linas Vepstas
2005-07-13 1:33 ` Hidetoshi Seto
2005-07-06 5:07 ` [PATCH 2.6.13-rc1 04/10] " Hidetoshi Seto
2005-07-06 5:11 ` [PATCH 2.6.13-rc1 05/10] " Hidetoshi Seto
2005-07-18 19:21 ` Grant Grundler
2005-07-06 5:14 ` [PATCH 2.6.13-rc1 06/10] " Hidetoshi Seto
2005-07-06 5:17 ` [PATCH 2.6.13-rc1 07/10] " Hidetoshi Seto
2005-07-08 4:37 ` david mosberger
2005-07-08 5:44 ` Hidetoshi Seto
2005-07-08 19:05 ` Luck, Tony
2005-07-08 19:23 ` david mosberger
2005-07-08 20:17 ` Luck, Tony
2005-07-11 17:51 ` Jesse Barnes
2005-07-11 18:21 ` Luck, Tony
2005-07-11 19:21 ` david mosberger [this message]
2005-07-12 21:14 ` Linas Vepstas
2005-07-13 1:59 ` Hidetoshi Seto
2005-07-06 5:18 ` [PATCH 2.6.13-rc1 08/10] " Hidetoshi Seto
2005-07-12 22:22 ` Linas Vepstas
2005-07-13 1:36 ` Hidetoshi Seto
2005-07-06 5:20 ` [PATCH 2.6.13-rc1 09/10] " Hidetoshi Seto
2005-07-06 5:21 ` [PATCH 2.6.13-rc1 10/10] " Hidetoshi Seto
2005-07-06 6:26 ` [PATCH 2.6.13-rc1 01/10] IOCHK interface for I/O error
2005-07-06 10:15 ` [PATCH 2.6.13-rc1 01/10] IOCHK interface for I/O error handling/detecting Hidetoshi Seto
2005-07-07 18:41 ` Greg KH
2005-07-07 22:27 ` [PATCH 2.6.13-rc1 01/10] IOCHK interface for I/O error Benjamin Herrenschmidt
2005-07-08 12:22 ` [PATCH 2.6.13-rc1 01/10] IOCHK interface for I/O error handling/detecting Hidetoshi Seto
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=ed5aea4305071112212756924@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