search for: writepages

Hi all, we got a new test system here and I just also tested btrfs raid6 on that. Write performance is slightly lower than hw-raid (LSI megasas) and md-raid6, but it probably would be much better than any of these two, if it wouldn''t read all the during the writes. Is this a known issue? This is with linux-3.9.2. Thanks, Bernd -- To unsubscribe from this list: send the line

Hey I am playing with a LOT of threads right now, and I want to know if the threads all need their own little vorbis encoders running in them or what exactly is threadsafe in vorbis? So here are the functions that would be called from many threads of with buffer = vorbis_analysis_buffer( &m_vorbisDsp, 4*DATA_CHUNK_SIZE ); vorbis_analysis_wrote( &m_vorbisDsp, dataLength/dataSize );

Hi. I introduced "is_partially_uptodate" aops for OCFS2. A page can have multiple buffers and even if a page is not uptodate, some buffers can be uptodate on pagesize != blocksize environment. This aops checks that all buffers which correspond to a part of a file that we want to read are uptodate. If so, we do not have to issue actual read IO to HDD even if a page is not uptodate

...80 c1275e98 00000000 c016598a Sep 21 23:10:05 devil kernel: c95c4e84 00000000 c9f65e90 00000001 c95c4f0c c9f65f70 00000000 00000004 Sep 21 23:10:05 devil kernel: c95c4f0c c9f65e58 fffffffc c9f65ee0 c95c4f3c c95c4f2c c95c4f1c c9f64000 Sep 21 23:10:05 devil kernel: Call Trace: [mpage_writepages+990/1971] [filemap_nopage+243/612] [do_no_page+617/784] [handle_mm_fault+149/360] [__set_page_dirty_buffers+344/404] Sep 21 23:10:05 devil kernel: [filemap_sync_pte+106/116] [ext3_writepages+31/48] [ext3_get_block+0/104] [do_writepages+24/44] [filemap_fdatawrite+93/112] [msync_interval+102/196]...

On Thu, Mar 07, 2019 at 02:38:38PM -0500, Andrea Arcangeli wrote: > On Thu, Mar 07, 2019 at 02:09:10PM -0500, Jerome Glisse wrote: > > I thought this patch was only for anonymous memory ie not file back ? > > Yes, the other common usages are on hugetlbfs/tmpfs that also don't > need to implement writeback and are obviously safe too. > > > If so then set dirty is

On Thu, Mar 07, 2019 at 02:38:38PM -0500, Andrea Arcangeli wrote: > On Thu, Mar 07, 2019 at 02:09:10PM -0500, Jerome Glisse wrote: > > I thought this patch was only for anonymous memory ie not file back ? > > Yes, the other common usages are on hugetlbfs/tmpfs that also don't > need to implement writeback and are obviously safe too. > > > If so then set dirty is

---------- Forwarded Message ---------- Subject: ext3 for 2.4 Date: Thu, 17 May 2001 21:20:38 +1000 From: Andrew Morton <andrewm@uow.edu.au> To: ext2-devel@lists.sourceforge.net, "Peter J. Braam" <braam@mountainviewdata.com>, Andreas Dilger <adilger@turbolinux.com>, "Stephen C. Tweedie" <sct@redhat.com> Cc: linux-fsdevel@vger.kernel.org Summary:

On Wed, Jan 18, 2023 at 06:30:20PM +0100, Christoph Hellwig wrote: > Hi all, > > this series removes most users of the write_one_page API. These helpers > internally call ->writepage which we are gradually removing from the > kernel. > > Changes since v2: > - more minix error handling fixes > > Changes since v1: > - drop the btrfs changes (queue up in the

Use filemap_write_and_wait_range to write back the range of the dirty page instead of write_one_page in preparation of removing write_one_page and eventually ->writepage. Signed-off-by: Christoph Hellwig <hch at lst.de> Reviewed-by: Jan Kara <jack at suse.cz> Reviewed-by: Joseph Qi <joseph.qi at linux.alibaba.com> --- fs/ocfs2/refcounttree.c | 9 +++++---- 1 file changed, 5

A while back, after 2.5.6, there were various changes made to the kernel that resulted in some instability with journaled data on ext3 filesystems, as well as small issues with my 2k block size file systems. Can someone (say, Andrew Morton ;) comment on the stability of the current release with this sort of configuration? If it's not full of known bugs then I will give it another shot, but I

Hi all, this series removes most users of the write_one_page API. These helpers internally call ->writepage which we are gradually removing from the kernel. Changes since v3: - drop all patches merged in v6.3-rc1 - re-add the jfs patch Changes since v2: - more minix error handling fixes Changes since v1: - drop the btrfs changes (queue up in the btrfs tree) - drop the finaly move to

Hello Jerome, On Thu, Mar 07, 2019 at 03:17:22PM -0500, Jerome Glisse wrote: > So for the above the easiest thing is to call set_page_dirty() from > the mmu notifier callback. It is always safe to use the non locking > variant from such callback. Well it is safe only if the page was > map with write permission prior to the callback so here i assume > nothing stupid is going on and

...uster coherent. > - quotas > - cluster aware flock <---------------------------------------- > - Directory change notification (F_NOTIFY) > - Distributed Caching (F_SETLEASE/F_GETLEASE/break_lease) > - POSIX ACLs > - readpages / writepages (not user visible) If this is an ill-informed question, please enlighten me. I'm following this list for quite some time and have done some tests (quite some time ago) and noticed then that if you write from two machines to the same file at the same moment, the one that is finished last 'w...

Hi all, this series removes most users of the write_one_page API. These helpers internally call ->writepage which we are gradually removing from the kernel. Changes since v2: - more minix error handling fixes Changes since v1: - drop the btrfs changes (queue up in the btrfs tree) - drop the finaly move to jfs (can't be done without the btrfs patches) - fix the existing minix code to

On 2019/3/8 ??5:27, Andrea Arcangeli wrote: > Hello Jerome, > > On Thu, Mar 07, 2019 at 03:17:22PM -0500, Jerome Glisse wrote: >> So for the above the easiest thing is to call set_page_dirty() from >> the mmu notifier callback. It is always safe to use the non locking >> variant from such callback. Well it is safe only if the page was >> map with write permission

On 2019/3/8 ??5:27, Andrea Arcangeli wrote: > Hello Jerome, > > On Thu, Mar 07, 2019 at 03:17:22PM -0500, Jerome Glisse wrote: >> So for the above the easiest thing is to call set_page_dirty() from >> the mmu notifier callback. It is always safe to use the non locking >> variant from such callback. Well it is safe only if the page was >> map with write permission

On Wed, Jan 18, 2023 at 09:23:37PM +0000, Al Viro wrote: > On Wed, Jan 18, 2023 at 06:30:20PM +0100, Christoph Hellwig wrote: > > Hi all, > > > > this series removes most users of the write_one_page API. These helpers > > internally call ->writepage which we are gradually removing from the > > kernel. > > > > Changes since v2: > > - more

I have been studying this for the last several days, and the one thing that leaps out at me is that the page cache always flushes one page at a time. Always. To some extent, there is justification for this - what has to happen for each page that gets flushed depends in part on what file system is being written to and whether or not there is a function for that file system to handle the pages.

The patch titled Subject: ocfs2: don't use write_one_page in ocfs2_duplicate_clusters_by_page has been added to the -mm mm-unstable branch. Its filename is ocfs2-dont-use-write_one_page-in-ocfs2_duplicate_clusters_by_page.patch This patch will shortly appear at

On 6/29/07, Wojtek.Pilorz <wpilorz at bdk.pl> wrote: > On Fedora6, I have noted the folowing problems when using cifs to connect to > NT shares: > > - cp -vip does not copy mtime; tar x does copy mtime > (it seems setting modtime by fname does work, setting by handle does not) > - when there is a share mounted from a NT/2000 server which is not used for long time >