similar to: performance gain in data journalling mode

An update to the ext3 filesystem for 2.4 kernels is available at http://www.uow.edu.au/~andrewm/linux/ext3/ The diffs are against linux-2.4.7 and linux-2.4.6-ac5. The changelog is there. One rarely-occurring but oopsable bug was fixed and several quite significant performance enhancements have been made. These are in addition to the performance fixes which went into 0.9.3. Ted has put out a

IHAC using ZFS in production, and he''s opening up some files with the O_SYNC flag. This affects subsequent write()''s by providing synchronized I/O file integrity completion. That is, each write(2) will wait for both the file data and file status to be physically updated. Because of this, he''s seeing some delays on the file write()''s. This is verified with

On Fri, Aug 07, 2020 at 05:29:24PM +0300, Nir Soffer wrote: > On Fri, Aug 7, 2020 at 5:07 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > These ones? > > https://www.redhat.com/archives/libguestfs/2020-August/msg00078.html > > No, we had a bug when copying image from glance caused sanlock timeouts > because of the unpredictable page cache flushes. > > We

Hi, I'm running dovecot on a small server. I put all my mail from the last 10 years on it (approx. 160 mb). I'm seeing terrible performance. Sometimes, my client needs several minutes to display a message. This is with mutt, thunderbird and evolution. Copying an outbound message to the Sent IMAP folder (15k messages) typically takes a few minutes, but can be quite fast on occasion

OK. Thank you. What I want to do is: Fix source code in-place, then feed it to compiler normally. I assume I can fix source code in-place using clang::SourceManager, but I cannot find the appropriate API. Now I know that way is infeasible. Thanks again. 2011/5/5 Joshua Warner <joshuawarner32 at gmail.com> > Wen-Han, > > It sounds like there are two problems here: first is

Thanks very much for all of your answer. I was confused by definition of 'portable' by my own thinking. Now I Correct that. (ILP32 is in another project, It's my typo. Thanks) So let me make a conclusion about this. LLVM IR can be a portable language, just depending on our front-end configuration or origin language limits. Did I mistake that? Thank a lot all of you. 2010/12/22

dovecot-request at dovecot.org wrote: >Am Samstag, 4. Juni 2005 01:31 schrieb Han-Wen Nienhuys: > >>> I'm seeing terrible performance. Sometimes, my client needs several> > >(...) > >>> How can I debug this problem? I'm running dovecot .99.14 on a Mac Mini >> (OS X 10.3, 512 mb, 80 gb). > >mbox or maildir? Maildir. Listing or

Dear all, I cannot find the answer of this question. We all know LLVM IR is portable, but it uses ILP32 and record the target layout within the IR. target datalayout = "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64 :64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64" target triple = "x86_64-linux-gnu" It seems it already assigned

Hello, We found that fsync and fdatasync syscalls sometimes don't sync data in an ext3 file system under the following conditions. 1. Kernel version is 2.6.6 or later (including 2.6.8.1 and 2.6.9-rc2). 2. Ext3's journalling mode is "data=journal". 3. Create a file (whose size is 1Mbytes) and execute umount/mount. 4. lseek to a random position within the file, write 8192 bytes

An update of the ext3 journalling filesystem for 2.4 kernels is available at http://www.uow.edu.au/~andrewm/linux/ext3/ Patches are against 2.4.6-ac1 and 2.4.6. Changes since 0.0.8 include: - Multiplied the version numbering by ten to cater for bugfix releases against the 0.9.0 stream. - The main thrust has been the removal of a number of changes in the core kernel which were required

Hi all, in this case: ... int* p = ... int* q = p; ... How can I know that data-flow from p to q, i.e., which LLVM pass of header files could I use? Thank you all. -- Best regards, Wen-Han -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110430/a9164c60/attachment.html>

Hi Stephen, I would like to know the behavior of ext3 for a write() request used with O_SYNC for 64 K in term of disk access method: - is there a chance to have only one disk access (instead of 16 x 4 K corresponding to each mapped page ) or at maximum two in journaled mode ? - if this is possible then how can i force such a grouping of data in a single disk output ? NB: i disable cached write

On Sat, Aug 08, 2020 at 02:14:22AM +0300, Nir Soffer wrote: > On Fri, Aug 7, 2020 at 5:36 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > > > On Fri, Aug 07, 2020 at 05:29:24PM +0300, Nir Soffer wrote: > > > On Fri, Aug 7, 2020 at 5:07 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > > > These ones? > > > >

Dear all, AFAIK, ARM EHABI is not ready for both asm and obj emitter. Some people including me what to implement them. My question is, to avoid duplicate effort, does someone take charge of this part? or does anyone is already implementing this currently? BTW, any suggestion on this effort? I'm very appreciated! Thanks in advance! -- Best regards, Wen-Han Gu (Nowar) -------------- next

Greetings all, I have a question regarding the fsync data corruption bug that was introduced in 2.4.20 when using data=journal. I have patched the 2.4.20 kernel with the 3 sync patches available from zip.com.au, and I am wondering if with these patches the "bug" still exists: sync_fs.patch sync_fs-fix.patch sync_fs-fix-2.patch In addition the following two patches have also

Sorry if this message has been posted by someone else before, but I couldn't find anything similar in the last couple of months of archive. The question is how safe is journalling, in general? The "ordered" mount option for ext3 seems pretty safe, but is it possible that if the drive's power went half way through writing to the journal, could it be left in an inconsistent state?

Dear all, I'm a beginner in LLVM field. If any rudeness, I feel sorry to that. I have checked-out the source and built successfully. Now I want to use it, so I write a simple code. // context.cpp #include "llvm/LLVMContext.h" int main() { llvm::LLVMContext& context = llvm::getGlobalContext(); return 0; } $ clang++ `llvm-config --cxxflags --ldflags --libs` context.cpp But

Dear all, I heard a different way to solve it. $ apt-get install libc6-dev-amd64 Maybe this can help? 2010/12/30 Anton Korobeynikov <anton at korobeynikov.info> > Hello > > > Thanks for the tip. My PS3 workstationn is installed a 32-bit OS. I will > Please carefully read the readme.llvm file in the llvm-gcc source > directory. > At least it will give some hints how

Hello all, I wanna build a static linked executable using llvm. But I failed. My question is Can we use -static using llvm? Thanks for any response. Below is details ======== First I use $ clang++ test.cc `llvm-config --cxxflags --ldflags --libs` I works as usual. But if I use $ clang++ test.cc `llvm-config --cxxflags --ldflags --libs` -static It yells lots of undefined reference, like

James R Grinter wrote:- > >On Fri, Jul 13, 2007 at 09:39:37AM +0100, Mac wrote: >> On one previous occasion, the whole thing seemed to grind to a virtual >> halt, and we suspected (but couldn't prove) that a locking battle over >> (something like) secrets.tdb was to blame. > >(I recognise that symptom, see below) > >> Something that stands out is a huge