linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hisashi Hifumi <hifumi.hisashi@oss.ntt.co.jp>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	linux-ext4@vger.kernel.org, cmm@us.ibm.com
Subject: Re: [PATCH] vmscan: set try_to_release_page's gfp_mask to 0
Date: Thu, 16 Oct 2008 12:06:09 +0900	[thread overview]
Message-ID: <6.0.0.20.2.20081016120032.046ec3a0@172.19.0.2> (raw)
In-Reply-To: <20081015195458.cc203dd5.akpm@linux-foundation.org>

At 11:54 08/10/16, Andrew Morton wrote:
>On Thu, 16 Oct 2008 11:44:39 +0900 Hisashi Hifumi 
><hifumi.hisashi@oss.ntt.co.jp> wrote:
>
>> 
>> Unfortunately, I did not succeed to get good performance number that
>> prove this patch had some benefit.
>
>OK, thanks, I dropped it.
>
>> >This patch remains in a stalled state...
>> >
>> >And then there's this:
>> >
>> 
>> >: 
>> >: Really, I think what this patch tells us is that 3f31fddf ("jbd: fix
>> >: race between free buffer and commit transaction") was an unpleasant
>> >: hack which had undesirable and unexpected side-effects.  I think - that
>> >: depends upon your as-yet-undisclosed testing results?
>> >: 
>> >: Perhaps we should revert 3f31fddf and have another think about how to
>> >: fix the direct-io -EIO problem.  One option would be to hold our noses
>> >: and add a new gfp_t flag for this specific purpose?
>> >:
>> 
>> direct-io -EIO problem was already fixed by following patch.
>> 
>> commit 6ccfa806a9cfbbf1cd43d5b6aa47ef2c0eb518fd
>> Author: Hisashi Hifumi <hifumi.hisashi@oss.ntt.co.jp>
>> Date:   Tue Sep 2 14:35:40 2008 -0700
>> 
>>     VFS: fix dio write returning EIO when try_to_release_page fails
>> 
>> Dio falls back to buffered write when dio write gets EIO due to failure 
>of try_to_release_page
>> by above patch. So I think just reverting the patch 3f31fddf ("jbd: fix 
>race between 
>> free buffer and commit transaction") is good approach.
>
>Fair enough.  Could I ask that you (or someone) send a suitable patch
>sometime?

Yes, sometimes I send you some bug fixing or performance improvement
patch.

>
>I could generate the patch, but I'd never get around to testing it. 
>Too busy fixing rejects and compile errors :(

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2008-10-16  3:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13  2:21 Hisashi Hifumi
2008-08-13  3:21 ` Andrew Morton
2008-08-13  6:24   ` Hisashi Hifumi
2008-10-15 22:36     ` Andrew Morton
2008-10-16  2:44       ` Hisashi Hifumi
2008-10-16  2:54         ` Andrew Morton
2008-10-16  3:06           ` Hisashi Hifumi [this message]

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=6.0.0.20.2.20081016120032.046ec3a0@172.19.0.2 \
    --to=hifumi.hisashi@oss.ntt.co.jp \
    --cc=akpm@linux-foundation.org \
    --cc=cmm@us.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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