[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <x49r4pvlata.fsf@segfault.boston.devel.redhat.com>
Date: Fri, 21 Sep 2012 10:17:37 -0400
From: Jeff Moyer <jmoyer@...hat.com>
To: Jagdish Motwani <jagdish.motwani@...tecore.com>
Cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: performance degradation on kernel upgrade (due to commit ab0a9735e06914ce4d2a94ffa41497dbc142fe7f )
Jagdish Motwani <jagdish.motwani@...tecore.com> writes:
> Recently i upgraded my kernel from 2.6.29.6 to 2.6.35.14.
>
> After upgrading i got very poor performance on my postgre database.
[...]
> Using git bisect, i got commit ab0a9735e06914ce4d2a94ffa41497dbc142fe7f
>
> Is it a behavior change or am i missing something? Are there any
> workarounds for this?
commit ab0a9735e06914ce4d2a94ffa41497dbc142fe7f
Author: Christoph Hellwig <hch@....de>
Date: Thu Oct 29 14:14:04 2009 +0100
blkdev: flush disk cache on ->fsync
This is a data integrity fix, and you really don't want to work around
it.
Cheers,
Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists