search for: incremente

I was testing ocfs2 on a 2 node cluster set up. ocfs2-tools version is 1.6.3 ocfs2 kernel version is 2.6.36 Using cman on 2 nodes node02 dw # ping_pong -rwm /data/test.dat 3 data increment = 2 14 locks/sec node01 dw # ping_pong -rw /data/test.dat 3 data increment = 2 10 locks/sec node02 dw # ping_pong -r /data/test.dat 3 1980 locks/sec Using cman on 1 node node02 dw #

On 11/9/2015 9:50 AM, Gordon Messmer wrote: > > I don't see the distinction you're making. a incremental backup copies everything since the last incremental a differential copies everything since the last full. rsync is NOT a backup system, its just a incremental file copy with the full/incremental/differential approach, a restore to a given date would need to restore the last

...ment to point to the next i8 value. So the post increment nature is in the Target. A normal i16 indirect load need to be converted to two post increment load. SDNodes can be used to define only one value and so the Selection DAG cannot to used to encode the information that the pointer has been incremented. I think the description that you mentioned will transform the addition/subtraction of a pointer and/from a constant into a pointer and an offset(Please correct me if i am wrong). We are doing this transformation in the Lowering of the Loads and stores. Does the Machine Instruction class prov...

I try to track down an error that causes that Astcc just reports the time, but not the costs. I could narrow the problem down into this sub routine: sub calccost() { my ($adjconn, $adjcost, $answeredtime, $increment) = @_; eval { my $adjtime = int(($answeredtime + $increment - 1) / $increment) * $increment }; my $cost; print STDERR "Adjusted time is $adjtime, cost is $adjcost with

Hi all, I have the following situation: Backup /mysource to /backupdir, /backupdir/full ---------an old full backup /backupdir/back2 -------previous increment backup(based on the full backup mentioned above) /backupdir/back1 ------most recent increment backup (based on the two backups mentioned above) How can I merge the two increment backups into one directory,say

The method is here: https://github.com/rails/rails/blob/master/activerecord/lib/active_record/persistence.rb#L288. The method takes the in-memory attribute value and increments it by the specified amount. A safer approach (from an isolation standpoint) would be to let the database determine the value. Instead of telling the database what value to persist in the database, the SQL can written

...crement nature >> is >> in the Target. A normal i16 indirect load need to be converted to two >> post increment load. SDNodes can be used to define only one value and >> so >> the Selection DAG cannot to used to encode the information that the >> pointer has been incremented. > This is not true. SDNodes can have multiple values. Load SD nodes can have different addressing modes (PRE_INC, POST_INC, etc.) and for PRE_INC and POST_INC, the SDNode returns multiple values. If you look in lib/CodeGen/SelectionDAG/DAGCombiner.cpp in DAGCombiner::CombineToPostIndexedLoadSt...

for example's sake: With traditional backup systems, you keep a base (full backup, let's say every 30 days), then build incrementals on top of that, eg. (what has changed since the base). So, to restore, you copy over your base, then copy each incremental over the base to rebuild up to the latest snapshot. (*copying new incrementals files over older base files*) With rsync, (using

...a problem that I wish that I had ;) -- PPC does not have post-increment loads and stores, only pre-increment ones. Nevertheless, I think that the situation is similar... For one thing, I recently committed an enhancement to pre-increment generation that causes later constant offsets to use the new incremented address instead of the old address. I thought that this would not be an issue for post-increment generation, but it seems that I was wrong: you'd have the same problem here: if you post-increment the load and not the store, then you might need an extra register to hold the original base addres...

...ad ;) -- PPC does not > have post-increment loads and stores, only pre-increment ones. > Nevertheless, I think that the situation is similar... > > For one thing, I recently committed an enhancement to pre-increment > generation that causes later constant offsets to use the new > incremented address instead of the old address. I thought that this > would not be an issue for post-increment generation, but it seems that > I was wrong: you'd have the same problem here: if you post-increment > the load and not the store, then you might need an extra register to > hold the...

...i8 value. So the post increment nature > is > in the Target. A normal i16 indirect load need to be converted to two > post increment load. SDNodes can be used to define only one value and > so > the Selection DAG cannot to used to encode the information that the > pointer has been incremented. This is not true. SDNodes can have multiple values. Load SD nodes can have different addressing modes (PRE_INC, POST_INC, etc.) and for PRE_INC and POST_INC, the SDNode returns multiple values. If you look in lib/CodeGen/SelectionDAG/DAGCombiner.cpp in DAGCombiner::CombineToPostIndexedLoadStore...

Hi, We have an architecture where the indirect move instruction implicitly increments the pointer value after the move. We have Instruction format and pattern for this type of instructions. How to encode the information that the pointer is incremented? Thanks and regards, Shashidhar

I'm relatively new to LLVM so apologies in advance if this is a dumb question. I've been experimenting with re-targeting LLVM onto a 16-bit micro which has pre and post increment and decrement addressing modes. I've been using llvm-gcc to generate llvm bitcode and llvm 2.7 to go from here to my target assembly code. I've got the Combine pass to deal with

Hal, (and everyone who might care about post increment generation)... I have an interesting question/observation. Consider this vector loop. void vec_add_const(unsigned N, short __attribute__ ((aligned (16))) *A, short __attribute__ ((aligned (16))) val) { unsigned i,j; for (i=0; i<N; i++) { for (j=0; j<N; j++) { A[i*N+j] += val; } } } The

I have a rudimentary implementation for load and store instructions, where the memory address operand is automatically post-incremented when the load or store instruction is issued. However, this is currently coded using custom lowering, and explicit pattern matching in the 'ISelDAGtoDAG' implementation. But it seems to me that I ought to be able to achieve this exclusively using TableGen with minimal custom C++ code, bu...

So I thought I'd get a head start for next week - I have a low-power Linux box that has a few samba shares mounted, and limited hard disk space. This box is connected to a tape library via SCSI card. I want to find the best way to create a full, then incremental backup of the samba mounts, directly to tape. Some of the samba mounts are appliances that cannot run any special

I am trying to assign increasing trip numbers to a binary variable ("land"; 1=home and 0=away) where a string of 1's shouldn't increment the trip_no more than once. For example; based on land<-c(0,0,0,0,1,1,1,0,0,0,1,1,0,0,0,0) the "trip_no" sequence produced should be 1,1,1,1,2,2,2,2,2,2,3,3,3,3,3,3 This is as far as I can get but Im stumped. In addition I

...sage ----- > Hi, > > We have an architecture where the indirect move instruction > implicitly increments the pointer > value after the move. We have Instruction format and pattern for this > type of instructions. > > How to encode the information that the pointer is incremented? As you seem to be aware, LLVM has patterns specifically to match pre/post increment loads and stores (post_store). In your *ISelLowering.cpp file, you'll need to call setIndexedLoadAction(ISD::POST_INC, <type>, Legal), and the same for setIndexedStoreAction. Then you'll need to imp...

Hi all, Thanks for the incredibly quick help with the "%in%"... There's a second question, though: I'd like to increment an element of a vector if a certain event occurs, e.g. count[event] <- count[event] + 1; # works, but... Is this efficient? I wonder whether R needs to subset the count vector on both sides of the assignment operator (i.e., twice), or

Hi, Well, I need the procedure or how to do a full backup of archives to a directory. Then, do incremental backups in different directories. For example: source-dir to dest-dir a full backup. incremental of sources-dir and differential of backup-dir in `date +%m%h%y` Then, i should have a full backup in the dest-dir and incremental+diferential backup in every $DATE directory. Any ideas? I try