All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Brent Casavant <bcasavan@sgi.com>
Cc: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
	linux-ia64@vger.kernel.org,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6.13] IOCHK interface for I/O error handling/detecting (for ia64)
Date: Fri, 02 Sep 2005 18:24:53 +0000	[thread overview]
Message-ID: <20050902182453.GB28254@parisc-linux.org> (raw)
In-Reply-To: <20050901172917.I10072@chenjesu.americas.sgi.com>

On Thu, Sep 01, 2005 at 05:45:54PM -0500, Brent Casavant wrote:
> I am extremely concerned about the performance implications of this
> implementation.  These changes have several deleterious effects on I/O
> performance.

I agree.  I think the iochk patches should be abandoned and the feature
reimplemented on top of the asynchronous PCI error notification patches
from Linas Vepstas.

WARNING: multiple messages have this Message-ID (diff)
From: Matthew Wilcox <matthew@wil.cx>
To: Brent Casavant <bcasavan@sgi.com>
Cc: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
	linux-ia64@vger.kernel.org,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6.13] IOCHK interface for I/O error handling/detecting (for ia64)
Date: Fri, 2 Sep 2005 12:24:53 -0600	[thread overview]
Message-ID: <20050902182453.GB28254@parisc-linux.org> (raw)
In-Reply-To: <20050901172917.I10072@chenjesu.americas.sgi.com>

On Thu, Sep 01, 2005 at 05:45:54PM -0500, Brent Casavant wrote:
> I am extremely concerned about the performance implications of this
> implementation.  These changes have several deleterious effects on I/O
> performance.

I agree.  I think the iochk patches should be abandoned and the feature
reimplemented on top of the asynchronous PCI error notification patches
from Linas Vepstas.

  parent reply	other threads:[~2005-09-02 18:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-01  5:42 [PATCH 2.6.13] IOCHK interface for I/O error handling/detecting Hidetoshi Seto
2005-09-01  5:42 ` Hidetoshi Seto
2005-09-01  5:42 ` [PATCH 2.6.13] IOCHK interface for I/O error handling/detecting (for Hidetoshi Seto
2005-09-01  5:42   ` [PATCH 2.6.13] IOCHK interface for I/O error handling/detecting (for ia64) Hidetoshi Seto
2005-09-01 22:45   ` [PATCH 2.6.13] IOCHK interface for I/O error handling/detecting Brent Casavant
2005-09-01 22:45     ` [PATCH 2.6.13] IOCHK interface for I/O error handling/detecting (for ia64) Brent Casavant
2005-09-02 10:32     ` [PATCH 2.6.13] IOCHK interface for I/O error handling/detecting Hidetoshi Seto
2005-09-02 10:32       ` [PATCH 2.6.13] IOCHK interface for I/O error handling/detecting (for ia64) Hidetoshi Seto
2005-09-02 10:32     ` [PATCH 2.6.13 1/2] IOCHK interface for I/O error handling/detecting Hidetoshi Seto
2005-09-02 10:32       ` [PATCH 2.6.13 1/2] IOCHK interface for I/O error handling/detecting (for ia64) Hidetoshi Seto
2005-09-03  7:43       ` [PATCH 2.6.13 1/2] IOCHK interface for I/O error handling/detecting Hidetoshi Seto
2005-09-03  7:43         ` [PATCH 2.6.13 1/2] IOCHK interface for I/O error handling/detecting (for ia64) Hidetoshi Seto
2005-09-02 10:32     ` [PATCH 2.6.13 2/2] IOCHK interface for I/O error handling/detecting Hidetoshi Seto
2005-09-02 10:32       ` [PATCH 2.6.13 2/2] IOCHK interface for I/O error handling/detecting (for ia64) Hidetoshi Seto
2005-09-02 16:48     ` [PATCH 2.6.13] " Grant Grundler
2005-09-02 16:48       ` Grant Grundler
2005-09-02 18:16       ` david mosberger
2005-09-02 18:16         ` david mosberger
2005-09-02 22:23         ` Grant Grundler
2005-09-02 22:23           ` Grant Grundler
2005-09-02 18:24     ` Matthew Wilcox [this message]
2005-09-02 18:24       ` Matthew Wilcox
2005-09-03  9:36       ` [PATCH 2.6.13] IOCHK interface for I/O error handling/detecting Hidetoshi Seto
2005-09-03  9:36         ` [PATCH 2.6.13] IOCHK interface for I/O error handling/detecting (for ia64) 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=20050902182453.GB28254@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=bcasavan@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seto.hidetoshi@jp.fujitsu.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 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.