From mboxrd@z Thu Jan 1 00:00:00 1970 From: Suresh Jayaraman Subject: Re: [PATCH 3/6] CIFS: Make write call work with strict cache mode (try #2) Date: Wed, 01 Dec 2010 15:16:33 +0530 Message-ID: <4CF61979.5080505@suse.de> References: <1290931972-2770-1-git-send-email-piastryyy@gmail.com> <1290931972-2770-4-git-send-email-piastryyy@gmail.com> <20101128063604.7d9cdded@tlielax.poochiereds.net> <20101128065100.51c8a404@tlielax.poochiereds.net> <20101129063713.0b71ac09@tlielax.poochiereds.net> <4CF39901.3010108@suse.de> <4CF3D3D9.3060500@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: Jeff Layton , linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Pavel Shilovsky Return-path: In-Reply-To: Sender: linux-cifs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: On 11/29/2010 10:38 PM, Pavel Shilovsky wrote: > 2010/11/29 Suresh Jayaraman : >> On 11/29/2010 05:56 PM, Pavel Shilovsky wrote: >>> >>> What's about mmap and fsync patch? How do you think they mix with fscache? >>> >> >> Basically, relinquishing cookie when you are invalidating inode should >> make them work without issues I think. But, I would also test your >> patches (once you post the patchset that includes fscache handling as >> well) to be sure. >> >> > > I reposted patches from 2 to 5(included). So, uptodate set is > > Pavel Shilovsky (6): > CIFS: Make cifsFileInfo_put work with strict cache mode (try #4) > CIFS: Make read call work with strict cache mode (try #3) > CIFS: Make write call work with strict cache mode (try #3) > CIFS: Make cifs_fsync work with strict cache mode (try #3) > CIFS: Make cifs_file_map work with strict cache mode (try #3) > CIFS: Add strictcache mount option (try #2) > I just applied your patches on my test box, but I see that the fscache integration is not done, yet. Am I seeing older version of patches? -- Suresh Jayaraman