From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wu Fengguang Subject: Re: [PATCH] NFS: introduce writeback wait queue Date: Tue, 6 Oct 2009 08:12:12 +0800 Message-ID: <20091006001212.GA6241@localhost> References: <20091004030153.GA20327@localhost> <20091004030504.GA20644@localhost> <20091005110010.GW26573@kernel.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Trond Myklebust , Andrew Morton , "linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , LKML , "linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" To: Jens Axboe Return-path: Content-Disposition: inline In-Reply-To: <20091005110010.GW26573-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org> Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-fsdevel.vger.kernel.org On Mon, Oct 05, 2009 at 07:00:11PM +0800, Jens Axboe wrote: > On Sun, Oct 04 2009, Wu Fengguang wrote: > > Hi Jens, > > > > This is a bug fix for 2.6.32. Maybe other not block-queue based > > filesystems will have similar issues .. > > Not that I'm aware of, the NFS use is fairly special. Given that this is Sorry for the confusion. 2.6.32 is safe. I tested NFS, fuse and cifs. NFS writes will be throttled at the dirty limit, and fuse/cifs see near zero nr_writeback/nr_dirty numbers during heavy write. NFS and fuse does set the bdi congestion state and somehow expects it to backoff background flushing. This IO priority thing could be fixed for next merged window. > purely in the realm of nfs/, I'll let Trond decide how to include and > push this (when a final patch is agreed upon). > > Thanks for looking into this! Thanks, Fengguang -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html