- 31 Dec, 2008 1 commit
-
-
Edward Shishkin authored
copies. Signed-off-by: Edward Shishkin<edward.shishkin@gmail.com> Signed-off-by:Andrew Morton <akpm@linux-foundation.org>
-
- 06 Jan, 2009 1 commit
-
-
Edward Shishkin authored
. add support of loop devices over cryptcompress files. Signed-off-by:
Edward Shishkin <edward.shishkin@gmail.com> Signed-off-by:
-
- 17 Sep, 2009 1 commit
-
-
Vladimir Saveliev authored
Q&A wrt this patch: - A really short guide to how to get up and running with this filesystem. Reiser4 is a file system based on dancing tree algorithms, and is described at http://www.namesys.com. One should be able to get it up and running just like any of the other filesystems supported by Linux. Configure it to be compiled either builtin or as a module. Create reiser4 filesystem with mkfs.reiser4, mount and use it. More detailed info can be found at http://thebsh.namesys.com/snapshots/LATEST/READ.ME. - The direct URL which people use to obtain the mkfs tool for this filesystem. Also fsck and anything else. Reiser4 userland tools can be obtained at ftp://ftp.namesys.com/pub/reiser4progs. ftp://ftp.namesys.com/pub/reiser4progs/README contains detailed instructions on how to compile and install these tools. Also all reiser4 progs have man pages. - Any known shortcomings, caveats, etc. Reiser4 has been tested on i386 yet only. Quota support is not ready yet. Should be ready soon. Reiser4 was tested extensively, and we got to where the mailing list was not able to hit any bugs, but then we told people that, got an order of magnitude increase in users, and they are able to hit bugs that we are working on now. Reiser's Law of Software Engineering: Each order of magnitude increase in users finds more bugs, in a quantity equal to the previous order of magnitude increase in users. Success for software developers is measured by how long the frustration lasts. Only the very core functionality is working. Exotic plugins, an API for multiple operation transactions and accessing multiple small files in one syscall, compression, inheritance, all have been postponed until after the core functionality is shipped. The compression plugin needs a code review before anyone should use it. - A statement on compatibility with reiserfs3 filesytems. To upgrade from reiserfs V3 to V4, use tar, or sponsor us to write a convertfs. - Bear in mind that people will immediately benchmark this filesytem, and first impressions count. Now is your chance to communicate any tuning guidelines, mount options or whatever which you'd like people to understand BEFORE they start publishing benchmark info. Reiser4 is not tuned for fsync/sync/O_SYNC performance yet. If you see results that are much different from those at www.namesys.com/benchmarks.html, let us know. If you see performance characteristics that don't quite make sense, email reiserfs-list@namesys.com, such things are always of interest. reiser4 is not tuned for mmaping and dirtying more than physical ram like IOzone does. This is quite different in its code path from writing and dirtying more than physical ram. There are those who think that what IOZone does is rarely done by real programs, and therefor we should not bother to optimize what it does. All I know is, this month we are not optimized for it. Please consider its space savings when you benchmark it also. [michal.k.k.piotrowski@gmail.com: kill #include "linux/config.h"] [akpm@linux-foundation.org: reiser4_drop_page: don't call remove_from_page_cache] [bunk@stusta.de: fs/reiser4/: possible cleanups] Signed-off-by:Vladimir Saveliev <vs@namesys.com> Signed-off-by:
Hans Reiser <reiser@namesys.com> Signed-off-by:
Edward Shishkin <edward@namesys.com> DESC reiser4: fix for drop-unused-semaphores.patch EDESC Wait for tail conversion completion when acquiring exclusive access by . mmap_unix_file() . setattr_unix_file() . release_unix_file() Update comments. Signed-off-by:
Nate Diller <nate.diller@gmail.com> Cc: Vladimir Saveliev <vs@namesys.com> Cc: Edward Shishkin <edward@namesys.com> DESC reiser4-fix EDESC DESC reiser4: use zero_user_page EDESC Use zero_user_page() instead of open-coding it. Signed-off-by:
Laurent Riffard <laurent.riffard@free.fr> Acked-by:
Jens Axboe <jens.axboe@oracle.com> Acked-by:
Rusty Russell <rusty@rustcorp.com.au> Cc: Vladimir Saveliev <vs@namesys.com> Acked-by:
Dave Hansen <haveblue@us.ibm.com> Cc: Edward Shishkin <edward@namesys.com> Cc: "Vladimir V. Saveliev" <vs@namesys.com> DESC reiser4: fix extent2tail EDESC Fixed bug in extent2tail conversion. Bug description: when converting partially converted file (with flag REISER4_PART_MIXED installed) reiser4_cut_tree() starts to cut old metatada from wrong offset. Result is data corruption. Signed-off-by:
Zan Lynx <zlynx@acm.org> Cc: "Vladimir V. Saveliev" <vs@namesys.com> DESC git-block-vs-reiser4 EDESC Hope this is right. Hope you know what you're doing ;) Cc: Vladimir Saveliev <vs@namesys.com> Cc: Edward Shishkin <edward@namesys.com> Cc: Jens Axboe <jens.axboe@oracle.com> DESC reiser4: cryptcompress misc fixups EDESC . Fix a race (reproducible by fsx + sync (1)) between checkin_page_cluster operations: serialize them via special per-inode checkin_mutex (usual i_mutex is not suitable for this purpose, as ->writepages() also calls checkin_page_cluster(); . Add comments for checkin/checkout technique for synchronization of primary and secondary caches with proof of correctness; . Fix missed right neighbor when updating disk clusters by handle_pos_on_leaf() during squalloc (should use upper levels to get expected non-connected neighbor); . Resolve a race between read and truncate (when read finds partially truncated and, hence, unrecoverable disk cluster) via keeping a track of leftmost truncated disk clusters in cryptcompress-specific part of inode; . Introduce size translators and size modulators for common needs; . Update comments; . Rename badly sounding function names; . Fix coding style; . Add my part of credits. Signed-off-by:
Adrian Bunk <bunk@kernel.org> Cc: Edward Shishkin <edward@namesys.com> Cc: "Vladimir V. Saveliev" <vs@namesys.com> DESC reiser4: change error code base EDESC Change REISER4_ERROR_CODE_BASE to 10000 to not overlap real errnos Signed-off-by:
Mariusz Kozlowski <m.kozlowski@tuxland.pl> Cc: Edward Shishkin <edward@namesys.com> Cc: "Vladimir V. Saveliev" <vs@namesys.com> DESC reiser4: kmalloc + memset conversion to kzalloc EDESC Signed-off-by:
Pavel Emelyanov <xemul@openvz.org> DESC Subject: [PATCH 1/2] remove asm/bitops.h includes EDESC remove asm/bitops.h includes including asm/bitops directly may cause compile errors. don't include it and include linux/bitops instead. next patch will deny including asm header directly. Cc: Adrian Bunk <bunk@kernel.org> Signed-off-by:
Jiri Slaby <jirislaby@gmail.com>
-
- 11 Nov, 2009 5 commits
-
-
james toy authored
-
Andrew Morton authored
Reported-by:
Randy Dunlap <randy.dunlap@oracle.com> Signed-off-by:
-
Hans Reiser authored
add_to_page_cache_lru to be EXPORT_SYMBOL-ed. [bunk@stusta.de: unexport {,__}remove_from_page_cache] Signed-off-by:Adrian Bunk <bunk@stusta.de> Signed-off-by:
-
Artem Bityutskiy authored
generic implementaion and changes fs-writeback.c:sync_sb_inodes() to call filesystem's sync_inodes if it is defined or generic implementaion otherwise. This new operation allows filesystem to decide itself what to flush. Reiser4 flushes dirty pages on basic of atoms, not of inodes. sync_sb_inodes used to call address space flushing method (writepages) for every dirty inode. For reiser4 it caused having to commit atoms unnecessarily often. This turned into substantial slowdown. Having this method helped to fix that problem. akpm: this patch needs to be chnaged to remove the `sb' arg. Signed-off-by:
Artem Bityutskiy <Artem.Bityutskiy@nokia.com> Cc: Edward Shishkin <edward.shishkin@gmail.com> Signed-off-by:
-
Edward Shishkin authored
"captured" by some atom. However, outside reiser4 context dirty page can not be captured in some cases, as it is accompanied with specific work (jnode creation, etc). Reiser4 recognizes such "anonymous" pages (i.e. pages that were dirtied outside of reiser4) by the tag PAGECACHE_TAG_DIRTY. Pages dirtied inside reiser4 context are not tagged at all: we don't need this. Indeed, once page is dirtied and captured, it is attached to a jnode (a special header to keep a track of transactions). reiser4_set_page_dirty_internal() was the internal reiser4 function that set dirty bit without tagging the page. Having such internal function led to real problems (incorrect task io accounting, etc. because of not updating this internal "friend"). Solution: The following patch adds a core library function that sets a dirty bit without tagging the page. Signed-off-by: Edward Shishkin<edward.shishkin@gmail.com> Cc: Nick Piggin <nickpiggin@yahoo.com.au> Signed-off-by:
-
- 04 Jun, 2009 1 commit
-
-
Andrew Morton authored
Cc: David S. Miller <davem@davemloft.net> Cc: Florian Fainelli <florian@openwrt.org> Cc: Julius Volz <juliusv@google.com> Cc: Sergei Shtylyov <sshtylyov@ru.mvista.com> Cc: Simon Horman <horms@verge.net.au> Cc: Takashi Iwai <tiwai@suse.de> Cc: Patrick McHardy <kaber@trash.net> Signed-off-by:
-
- 17 Sep, 2009 1 commit
-
-
Florian Fainelli authored
lib/gcd.c, the latter also implementing the a < b case. Signed-off-by:
Florian Fainelli <florian@openwrt.org> Cc: Sergei Shtylyov <sshtylyov@ru.mvista.com> Cc: Takashi Iwai <tiwai@suse.de> Acked-by:
Simon Horman <horms@verge.net.au> Cc: Julius Volz <juliusv@google.com> Cc: David S. Miller <davem@davemloft.net> Cc: Patrick McHardy <kaber@trash.net> Signed-off-by:
-
- 04 Jun, 2009 1 commit
-
-
Florian Fainelli authored
Signed-off-by:
-
- 30 Oct, 2009 7 commits
-
-
Akinobu Mita authored
Signed-off-by: -
Akinobu Mita authored
Cc: Tony Luck <tony.luck@intel.com> Cc: Fenghua Yu <fenghua.yu@intel.com> Signed-off-by: -
Akinobu Mita authored
Acked-by:
"David S. Miller" <davem@davemloft.net> Signed-off-by:
-
Akinobu Mita authored
Reviewed-by:
Roland Dreier <rolandd@cisco.com> Cc: Yevgeny Petrilin <yevgenyp@mellanox.co.il> Signed-off-by:
-
Akinobu Mita authored
Cc: Greg Kroah-Hartman <gregkh@suse.de> Cc: Lothar Wassmann <LW@KARO-electronics.de> Signed-off-by: -
Akinobu Mita authored
1. s/iommu_area_free/bitmap_clear/ 2. s/iommu_area_reserve/bitmap_set/ 3. Use bitmap_find_next_zero_area instead of find_next_zero_area This cannot be simple substitution because find_next_zero_area doesn't check the last bit of the limit in bitmap 4. Remove iommu_area_free, iommu_area_reserve, and find_next_zero_area Signed-off-by:
Akinobu Mita <akinobu.mita@gmail.com> Cc: "David S. Miller" <davem@davemloft.net> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org> Cc: Paul Mackerras <paulus@samba.org> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Ingo Molnar <mingo@redhat.com> Cc: "H. Peter Anvin" <hpa@zytor.com> Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> Cc: Joerg Roedel <joerg.roedel@amd.com> Signed-off-by:
-
Akinobu Mita authored
bitmap_set: Set specified bit area bitmap_clear: Clear specified bit area bitmap_find_next_zero_area: Find free bit area These are mostly stolen from iommu helper. The differences are: - Use find_next_bit instead of doing test_bit for each bit - Rewrite bitmap_set and bitmap_clear Instead of setting or clearing for each bit. - Check the last bit of the limit iommu-helper doesn't want to find such area - The return value if there is no zero area find_next_zero_area in iommu helper: returns -1 bitmap_find_next_zero_area: return >= bitmap size Signed-off-by:
-
- 12 Nov, 2009 2 commits
-
-
Albin Tonnerre authored
Tested-by:
Wu Zhangjin <wuzhangjin@gmail.com> Cc: "H. Peter Anvin" <hpa@zytor.com> Cc: Ingo Molnar <mingo@elte.hu> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Russell King <rmk@arm.linux.org.uk> Cc: Ralf Baechle <ralf@linux-mips.org> Signed-off-by:
-
Albin Tonnerre authored
use of this new compression method Signed-off-by:
Albin Tonnerre <albin.tonnerre@free-electrons.com> Acked-by:
H. Peter Anvin <hpa@zytor.com> Tested-by:
-
- 13 Nov, 2009 1 commit
-
-
Albin Tonnerre authored
and Russell King Signed-off-by:
-
- 12 Nov, 2009 4 commits
-
-
Albin Tonnerre authored
compression types - new piggy.lzo.S necessary for lzo compression - changes in arch/arm/boot/compressed/misc.c to allow the use of lzo or gzip, depending on the config - Kconfig support Signed-off-by:
-
Andrew Morton authored
Cc: Albin Tonnerre <albin.tonnerre@free-electrons.com> Cc: Ingo Molnar <mingo@elte.hu> Cc: Ralf Baechle <ralf@linux-mips.org> Cc: Russell King <rmk@arm.linux.org.uk> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Wu Zhangjin <wuzhangjin@gmail.com> Signed-off-by: -
Andrew Morton authored
#184: FILE: lib/decompress_unlzo.c:48: +static const unsigned char lzop_magic[] = + { 0x89, 0x4c, 0x5a, 0x4f, 0x00, 0x0d, 0x0a, 0x1a, 0x0a }; WARNING: line over 80 characters #254: FILE: lib/decompress_unlzo.c:118: + error("Both input pointer and fill function provided, don't know what to do"); WARNING: line over 80 characters #259: FILE: lib/decompress_unlzo.c:123: + error("NULL input pointer and missing position pointer or fill function"); WARNING: line over 80 characters #313: FILE: lib/decompress_unlzo.c:177: + r = lzo1x_decompress_safe((u8 *) in_buf, src_len, out_buf, &tmp); total: 1 errors, 3 warnings, 291 lines checked ./patches/lib-add-support-for-lzo-compressed-kernels.patch has style problems, please review. If any of these errors are false positives report them to the maintainer, see CHECKPATCH in MAINTAINERS. Please run checkpatch prior to sending patches Cc: "H. Peter Anvin" <hpa@zytor.com> Cc: Albin Tonnerre <albin.tonnerre@free-electrons.com> Cc: Ingo Molnar <mingo@elte.hu> Cc: Ralf Baechle <ralf@linux-mips.org> Cc: Russell King <rmk@arm.linux.org.uk> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Wu Zhangjin <wuzhangjin@gmail.com> Signed-off-by: -
Albin Tonnerre authored
LZO-compressed kernel images, as well as support for using such images on the x86 and ARM architectures, and support for creating and using LZO-compressed initrd and initramfs images. This patch: The lzo compressor is worse than gzip at compression, but faster at extraction. Here are some figures for an ARM board I'm working on: Uncompressed size: 3.24Mo gzip 1.61Mo 0.72s lzo 1.75Mo 0.48s So for a compression ratio that is still relatively close to gzip, it's much faster to extract, at least in that case. This part contains: - Makefile routine to support lzo compression - Fixes to the existing lzo compressor so that it can be used in compressed kernels - wrapper around the existing lzo1x_decompress, as it only extracts one block at a time, while we need to extract a whole file here - config dialog for kernel compression Signed-off-by:
-
- 13 Nov, 2009 3 commits
-
-
Andrew Morton authored
#90: FILE: lib/zlib_inflate/inffast.c:250: + /* minimum length is three */$ ERROR: space prohibited before that close parenthesis ')' #97: FILE: lib/zlib_inflate/inffast.c:257: + if (dist > 2 ) { WARNING: suspect code indent for conditional statements (24, 28) #111: FILE: lib/zlib_inflate/inffast.c:271: + if (dist == 1) [...] + pat16 = (pat16 & 0xff) | ((pat16 & 0xff ) << 8); ERROR: space prohibited before that close parenthesis ')' #113: FILE: lib/zlib_inflate/inffast.c:273: + pat16 = (pat16 & 0xff) | ((pat16 & 0xff ) << 8); ERROR: space prohibited before that close parenthesis ')' #115: FILE: lib/zlib_inflate/inffast.c:275: + pat16 = (pat16 & 0xff00) | ((pat16 & 0xff00 ) >> 8); total: 4 errors, 1 warnings, 93 lines checked ./patches/zlib-optimize-inffast-when-copying-direct-from-output.patch has style problems, please review. If any of these errors are false positives report them to the maintainer, see CHECKPATCH in MAINTAINERS. Please run checkpatch prior to sending patches Cc: Joakim Tjernlund <Joakim.Tjernlund@transmode.se> Signed-off-by: -
Joakim Tjernlund authored
direct from output" case. This patch tries to optimize the direct copy procedure. Uses get_unaligned() but only in one place. The copy loop just above this one can also use this optimization, but I havn't done so as I have not tested if it is a win there too. On my MPC8321 this is about 17% faster on my JFFS2 root FS than the original. Signed-off-by:
Joakim Tjernlund <Joakim.Tjernlund@transmode.se> Cc: Roel Kluin <roel.kluin@gmail.com> Cc: Richard Purdie <rpurdie@rpsys.net> Cc: David Woodhouse <dwmw2@infradead.org> Signed-off-by:
-
Akinobu Mita authored
Signed-off-by:
Anders Larsen <al@alarsen.net> Cc: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by:
-
- 10 Oct, 2009 1 commit
-
-
Anders Larsen authored
commit 945ffe54 ("qnx4: remove write support") removed the (defunct) write support but missed a chunk of related, dead code. Signed-off-by:
-
- 12 Nov, 2009 1 commit
-
-
Jean Delvare authored
parameter can be marked const. Same for resource_type(). Signed-off-by:
Jean Delvare <khali@linux-fr.org> Reviewed-by:
WANG Cong <xiyou.wangcong@gmail.com> Cc: Greg KH <greg@kroah.com> Signed-off-by:
-
- 10 Nov, 2009 2 commits
-
-
Andrew Morton authored
#252: FILE: fs/direct-io.c:1212: + if (end > isize ) total: 1 errors, 0 warnings, 338 lines checked ./patches/direct-io-cleanup-blockdev_direct_io-locking.patch has style problems, please review. If any of these errors are false positives report them to the maintainer, see CHECKPATCH in MAINTAINERS. Please run checkpatch prior to sending patches Cc: Christoph Hellwig <hch@lst.de> Signed-off-by: -
Christoph Hellwig authored
different locking types and very confusing checks for some of them. The most complicated one is DIO_OWN_LOCKING for reads, which happens to not actually be used. This patch gets rid of the DIO_OWN_LOCKING - as mentioned above the read case is unused anyway, and the write side is almost identical to DIO_NO_LOCKING. The difference is that DIO_NO_LOCKING always sets the create argument for the get_blocks callback to zero, but we can easily move that to the actual get_blocks callbacks. There are four users of the DIO_NO_LOCKING mode: gfs already ignores the create argument and thus is fine with the new version, ocfs2 only errors out if create were ever set, and we can remove this dead code now, the block device code only ever uses create for an error message if we are fully beyond the device which can never happen, and last but not least XFS will need the new behavour for writes. Now we can replace the lock_type variable with a flags one, where no flag means the DIO_NO_LOCKING behaviour and DIO_LOCKING is kept as the first flag. Separate out the check for not allowing to fill holes into a separate flag, although for now both flags always get set at the same time. Also revamp the documentation of the locking scheme to actually make sense. Signed-off-by:
Christoph Hellwig <hch@lst.de> Cc: Dave Chinner <david@fromorbit.com> Cc: Badari Pulavarty <pbadari@us.ibm.com> Cc: Jeff Moyer <jmoyer@redhat.com> Cc: Jens Axboe <jens.axboe@oracle.com> Cc: Zach Brown <zach.brown@oracle.com> Cc: Al Viro <viro@zeniv.linux.org.uk> Cc: Alex Elder <aelder@sgi.com> Cc: Mark Fasheh <mfasheh@suse.com> Cc: Joel Becker <joel.becker@oracle.com> Signed-off-by:
-
- 30 Oct, 2009 2 commits
-
-
Andrew Morton authored
Cc: Zach Brown <zach.brown@oracle.com> Signed-off-by: -
Jeff Moyer authored
commit 848c4dd5 Author: Zach Brown <zach.brown@oracle.com> Date: Mon Aug 20 17:12:01 2007 -0700 dio: zero struct dio with kzalloc instead of manually This patch uses kzalloc to zero all of struct dio rather than manually trying to track which fields we rely on being zero. It passed aio+dio stress testing and some bug regression testing on ext3. This patch was introduced by Linus in the conversation that lead up to Badari's minimal fix to manually zero .map_bh.b_state in commit: 6a648fa7 It makes the code a bit smaller. Maybe a couple fewer cachelines to load, if we're lucky: text data bss dec hex filename 3285925 568506 1304616 5159047 4eb887 vmlinux 3285797 568506 1304616 5158919 4eb807 vmlinux.patched I was unable to measure a stable difference in the number of cpu cycles spent in blockdev_direct_IO() when pushing aio+dio 256K reads at ~340MB/s. So the resulting intent of the patch isn't a performance gain but to avoid exposing ourselves to the risk of finding another field like .map_bh.b_state where we rely on zeroing but don't enforce it in the code. Zach surmised that zeroing out the page array was what caused most of the problem, and suggested the approach taken in the attached patch for resolving the issue. Intel re-tested with this patch and saw a 0.6% performance gain (the original regression was 0.5%). Signed-off-by:
Jeff Moyer <jmoyer@redhat.com> Acked-by:
Zach Brown <zach.brown@oracle.com> Signed-off-by:
-
- 13 Nov, 2009 2 commits
-
-
Shaohua Li authored
Signed-off-by:
Shaohua Li <shaohua.li@intel.com> Cc: Jeff Moyer <jmoyer@redhat.com> Cc: Benjamin LaHaise <bcrl@kvack.org> Cc: Zach Brown <zach.brown@oracle.com> Signed-off-by:
-
Joe Perches authored
Acked-by:
Alan Cox <alan@linux.intel.com> Signed-off-by:
-
- 14 Oct, 2009 1 commit
-
-
Roel Kluin authored
Signed-off-by:
Roel Kluin <roel.kluin@gmail.com> Cc: Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by:
-
- 11 Nov, 2009 1 commit
-
-
Jan Beulich authored
comparison msut also be done using the last valid of the buffer in question. Also fix the open-coded instances in lib/swiotlb.c. Signed-off-by:
Jan Beulich <jbeulich@novell.com> Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> Cc: Becky Bruce <beckyb@kernel.crashing.org> Cc: "Luck, Tony" <tony.luck@intel.com> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org> Cc: Ingo Molnar <mingo@elte.hu> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: "H. Peter Anvin" <hpa@zytor.com> Signed-off-by:
-
- 30 Sep, 2009 2 commits
-
-
Nils Carlson authored
the patch as far as possible with correctible errors and things appear good. The DIMM mapping is correct for our board, but boards may differ. Signed-off-by:
Nils Carlson <nils.carlson@ludd.ltu.se> Acked-by:
Arthur Jones <ajones@riverbed.com> Signed-off-by:
Doug Thompson <dougthompson@xmission.com> Signed-off-by:
-
Nils Carlson authored
scrubbing rate, which is not constant but dependent on memory load. The rate returned by this driver is an estimate based on some experimentation, but is substantially closer to the truth than the speed supplied in the documentation. Also, scrubbing is done once, and then a done-bit is set. This means that to accomplish continuous scrubbing a re-enabling mechanism must be used. I have created the simplest possible such mechanism in the form of a work-queue which will check every five minutes. This interval is quite arbitrary but should be sufficient for all sizes of system memory. Signed-off-by:
-
