search for: writepag

Displaying 20 results from an estimated 29 matches for "writepag".

Did you mean: writepage
2013 May 23
11
raid6: rmw writes all the time?
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
2002 Mar 27
1
What exactly is threadsafe
...vorbis_analysis( &m_vorbisBlock, NULL ); vorbis_bitrate_addblock( &m_vorbisBlock ); while( vorbis_bitrate_flushpacket( &m_vorbisDsp, &m_oggPacket ) ) { /* weld the packet into the bitstream */ ogg_stream_packetin( &m_oggStream, &m_oggPacket ); writePage(); } } **Write Page looks like this**: int result; result = ogg_stream_pageout( &m_oggStream, &m_oggPage ); while( result != 0 ) { m_sink->write( (char*)m_oggPage.header, m_oggPage.header_len ); m_sink->write( (char*)m_oggPage.body, m_oggPage.body_len ); resul...
2009 Mar 05
1
[PATCH] OCFS2: Pagecache usage optimization on OCFS2
...c 2009-03-05 13:46:07.000000000 +0900 +++ linux-2.6.29-rc7/fs/ocfs2/aops.c 2009-03-05 13:50:59.000000000 +0900 @@ -1953,15 +1953,16 @@ static int ocfs2_write_end(struct file * } const struct address_space_operations ocfs2_aops = { - .readpage = ocfs2_readpage, - .readpages = ocfs2_readpages, - .writepage = ocfs2_writepage, - .write_begin = ocfs2_write_begin, - .write_end = ocfs2_write_end, - .bmap = ocfs2_bmap, - .sync_page = block_sync_page, - .direct_IO = ocfs2_direct_IO, - .invalidatepage = ocfs2_invalidatepage, - .releasepage = ocfs2_releasepage, - .migratepage = buffer_migrate_page, + .readp...
2002 Sep 22
2
Assertion failure in ext3_get_block() at inode.c:853: "handle != 0"
...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/19...
2019 Mar 07
3
[RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
...least optimize away the _lock from > set_page_dirty if it's anon/hugetlbfs/tmpfs, would be nice if there > was a clean way to do that. > > Now assuming we don't nak the use on ext4 VM_SHARED and we stick to > set_page_dirty_lock for such case: could you recap how that > __writepage ext4 crash was solved if try_to_free_buffers() run on a > pinned GUP page (in our vhost case try_to_unmap would have gotten rid > of the pins through the mmu notifier and the page would have been > freed just fine). So for the above the easiest thing is to call set_page_dirty() from the...
2019 Mar 07
3
[RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
...least optimize away the _lock from > set_page_dirty if it's anon/hugetlbfs/tmpfs, would be nice if there > was a clean way to do that. > > Now assuming we don't nak the use on ext4 VM_SHARED and we stick to > set_page_dirty_lock for such case: could you recap how that > __writepage ext4 crash was solved if try_to_free_buffers() run on a > pinned GUP page (in our vhost case try_to_unmap would have gotten rid > of the pins through the mmu notifier and the page would have been > freed just fine). So for the above the easiest thing is to call set_page_dirty() from the...
2001 May 17
0
Fwd: ext3 for 2.4
...2.4 than in 2.2, presumably because of better request merging. Much more work needs to go into benchmarking and performance tuning. - There's an issue with page_launder(): ext3_file_write() -> generic_file_write() -> __alloc_pages() -> page_launder() -> ext3_writepage() This is bad. It will cause ext3 to be reentered while it has a transaction open against a different fs. This will corrupt filesystems and can deadlock. Making ext3_file_write() set PF_MEMALLOC wasn't suitable. It easily causes 0-order allocation failures within generic_file_wr...
2023 Jan 18
1
remove most callers of write_one_page v3
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 btrfs tree) > - drop the finaly move to jfs (can't be done without the btrfs patches) >...
2023 Mar 07
1
[PATCH 2/3] ocfs2: don't use write_one_page in ocfs2_duplicate_clusters_by_page
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 insertions(+), 4 deletions(-) diff --git a/fs/ocfs2/refcounttree.c b/f...
2002 Jul 02
2
is EXT3 data=journal, 2K block size, 2.5 series kernel stable?
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
2023 Mar 07
3
remove most callers of write_one_page v4
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 jfs (can'...
2019 Mar 07
0
[RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
...t ways. I think ext4 is the most obvious because of the > kernel log trace it leaves behind. > > Bottom line is for set_page_dirty to be safe you need the following: > lock_page() > page_mkwrite() > set_pte_with_write() > unlock_page() I also wondered why ext4 writepage doesn't recreate the bh if they got dropped by the VM and page->private is 0. I mean, page->index and page->mapping are still there, that's enough info for writepage itself to take a slow path and calls page_mkwrite to find where to write the page on disk. > Now when loosing t...
2007 May 22
1
Re: Ocfs2-users Digest, Vol 41, Issue 21
...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 '...
2023 Jan 18
9
remove most callers of write_one_page v3
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 properly p...
2019 Mar 08
2
[RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
...vious because of the >> kernel log trace it leaves behind. >> >> Bottom line is for set_page_dirty to be safe you need the following: >> lock_page() >> page_mkwrite() >> set_pte_with_write() >> unlock_page() > I also wondered why ext4 writepage doesn't recreate the bh if they got > dropped by the VM and page->private is 0. I mean, page->index and > page->mapping are still there, that's enough info for writepage itself > to take a slow path and calls page_mkwrite to find where to write the > page on disk. >...
2019 Mar 08
2
[RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
...vious because of the >> kernel log trace it leaves behind. >> >> Bottom line is for set_page_dirty to be safe you need the following: >> lock_page() >> page_mkwrite() >> set_pte_with_write() >> unlock_page() > I also wondered why ext4 writepage doesn't recreate the bh if they got > dropped by the VM and page->private is 0. I mean, page->index and > page->mapping are still there, that's enough info for writepage itself > to take a slow path and calls page_mkwrite to find where to write the > page on disk. >...
2023 Jan 18
1
remove most callers of write_one_page v3
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 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...
2007 Apr 03
0
Page cache flushing algorithm question
...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. However, as far as I can tell, if the mapping data for a page does not exist (mapping->a_ops->writepage == NULL), it is handed to mpage_writepage() for buffer management and i/o submission, whereas almost all of the file systems that do map this function map it to block_write_full_page. These two functions use completely different algorithms for flushing a page from the cache, or at least it sure l...
2023 Mar 07
0
+ ocfs2-dont-use-write_one_page-in-ocfs2_duplicate_clusters_by_page.patch added to mm-unstable branch
...hch at lst.de> Subject: ocfs2: don't use write_one_page in ocfs2_duplicate_clusters_by_page Date: Tue, 7 Mar 2023 15:31:24 +0100 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. Link: https://lkml.kernel.org/r/20230307143125.27778-3-hch at lst.de 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> Cc: Changwei Ge <gechangwei at live.cn> Cc: Dave Kleikamp...
2007 Jul 09
1
kernels with cifs backport (Was: where is smbmount on centOS 5)
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 >