search for: tnodes

...me<-c(rep(100,20),200) ClassCode=c(rep("Local",20),rep("Freeway",1)) #Create data frame with test data EmmeData..<-data.frame(TNode=TNode,FNode=FNode,Volume=Volume,ClassCode=ClassCode) #Create list to store results LinkSum_<-list() #Create vecotrs to establish loops TNodes<-unique(EmmeData..$TNode) FNodes<-unique(EmmeData..$FNode) for(tn in TNodes){ for(fn in FNodes){ TF<-EmmeData..[EmmeData..$TNode==tn & EmmeData..$FNode==fn,] FT<-EmmeData..[EmmeData..$TNode==fn & EmmeData..$FNode==tn,] if(length(TF$TNode)...

Hi guys, When I am trying to define pattern in a multi class, I got something like this: “ multi class P_PAT<string sty, SDNode tNode> { def : Pat<( !cast<ValueType>(“v2” # sty) (tNode !cast<ValueType>(“v2” # sty):$src1, !cast<ValueType>(“v2” # sty):$src2) ), ( add !cast<ValueType>(“v2” # sty):$src1, !cast<ValueType>(“v2” #

From: Jason Gunthorpe <jgg at mellanox.com> This converts one of the two users of mmu_notifiers to use the new API. The conversion is fairly straightforward, however the existing use of notifiers here seems to be racey. Tested-by: Dennis Dalessandro <dennis.dalessandro at intel.com> Signed-off-by: Jason Gunthorpe <jgg at mellanox.com> --- drivers/infiniband/hw/hfi1/file_ops.c

From: Jason Gunthorpe <jgg at mellanox.com> This converts one of the two users of mmu_notifiers to use the new API. The conversion is fairly straightforward, however the existing use of notifiers here seems to be racey. Cc: Mike Marciniszyn <mike.marciniszyn at intel.com> Cc: Dennis Dalessandro <dennis.dalessandro at intel.com> Signed-off-by: Jason Gunthorpe <jgg at

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, I'm trying to wrap my head around something that happened in our environment. Basically, we noticed the error in /var/log/messages with no other errors. "Mar 16 13:38:02 dbo3 kernel: (3712,3):o2hb_do_disk_heartbeat:963 ERROR: Device "sdb1": another node is heartbeating in our slot!" Usually there are a

Hi, The -dot-cfg option of opt will write a diagram of an analyzed function's CFG to DOT format. If you then open the DOT file, you will see that the BasicBlocks are uniquely identified with hexadecimal addresses. For example, an edge from one block to another may look like: Node0x10026b0:s0 -> Node0x1004c20; I've been trying to figure out where these hexadecimal addresses

From: Jason Gunthorpe <jgg at mellanox.com> 8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1, scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where they only use invalidate_range_start/end and immediately check the invalidating range against some driver data structure to tell if the driver is interested. Half of them use an interval_tree, the others

From: Jason Gunthorpe <jgg at mellanox.com> 8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1, scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where they only use invalidate_range_start/end and immediately check the invalidating range against some driver data structure to tell if the driver is interested. Half of them use an interval_tree, the others

Hi, I am trying to get my kickstart file that worked under 5.1 to work under 5.2 centos x86_64. This is the error that I get. On the screen it says Exception occured and gives me the option to save it. This is that file. I dont see any odd that would cause it to crash. Can anyone help. My kickstart file is in the mix below. Seems to be related to network, my line seems fine (I think) for

Hi, Is the http://xenbits.xensource.com/linux-2.6-xen.hg tree still being updated? if not, what''s the preferred Linux tree to track that has all of the Xen bits? Thanks, Muli _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel