search for: opreat

...tors in R. Specifically, I am using XTS of length of minimum 120k elements. My problem is that I cannot display the vector (otherwise R crashes), I cannot plot it either (otherwise R crashes). That could be solved by reducing the amount of points. However, I have been performing some statistical opreations on is and even sd(myXTS) crashes R. By "crashes", I mean shuts down without any warning whatsoever. I use R 2.11.1 (64). Has anyone had the same kind of problem? Can we solve this? Best, -- Jeremie [[alternative HTML version deleted]]

...virtqueue metadata through kernel virtual > > address instead of copy_user() friends since they had too much > > overheads like checks, spec barriers or even hardware feature > > toggling like SMAP. This is done through setup kernel address through > > direct mapping and co-opreate VM management with MMU notifiers. > > > > Test shows about 23% improvement on TX PPS. TCP_STREAM doesn't see > > obvious improvement. > > I'm still waiting for some review from mst. > > If I don't see any review soon I will just wipe these changes from...

I have updated R 2.9.1 to 2.10.0. and JGR GUI 1.7. I am running Windows XP. I can't seem to get the JGR "Print" or "Help" functions to work. The system locks and requires me to "stop the process". In the past I have preferred the opreation and "feel" of JGR GUI. I realize that this help forum is for R; but, I am hoping that some other R-user is a JGR GUI user and might have a hint about this. At one point I received the following: **************************************************** Loading required package: rJava L...

...t(&msg.msg_iter, READ, vq->iov, 1, 1); err = sock->ops->recvmsg(sock, &msg, 1, MSG_DONTWAIT | MSG_TRUNC); pr_debug("Discarded rx packet: len %zd\n", sock_len); continue; } ... } This makes it possible to trigger a infinite while..continue loop through the co-opreation of two VMs like: 1) Malicious VM1 allocate 1 byte rx buffer and try to slow down the vhost process as much as possible e.g using indirect descriptors or other. 2) Malicious VM2 generate packets to VM1 as fast as possible Fixing this by checking against weight at the end of RX and TX loop...

...t(&msg.msg_iter, READ, vq->iov, 1, 1); err = sock->ops->recvmsg(sock, &msg, 1, MSG_DONTWAIT | MSG_TRUNC); pr_debug("Discarded rx packet: len %zd\n", sock_len); continue; } ... } This makes it possible to trigger a infinite while..continue loop through the co-opreation of two VMs like: 1) Malicious VM1 allocate 1 byte rx buffer and try to slow down the vhost process as much as possible e.g using indirect descriptors or other. 2) Malicious VM2 generate packets to VM1 as fast as possible Fixing this by checking against weight at the end of RX and TX loop...

...ries tries to access virtqueue metadata through kernel virtual > address instead of copy_user() friends since they had too much > overheads like checks, spec barriers or even hardware feature > toggling like SMAP. This is done through setup kernel address through > direct mapping and co-opreate VM management with MMU notifiers. > > Test shows about 23% improvement on TX PPS. TCP_STREAM doesn't see > obvious improvement. I'm still waiting for some review from mst. If I don't see any review soon I will just wipe these changes from patchwork as it serves no purpose t...

...ries tries to access virtqueue metadata through kernel virtual > address instead of copy_user() friends since they had too much > overheads like checks, spec barriers or even hardware feature > toggling like SMAP. This is done through setup kernel address through > direct mapping and co-opreate VM management with MMU notifiers. > > Test shows about 23% improvement on TX PPS. TCP_STREAM doesn't see > obvious improvement. > > Thanks Thanks this is queued for next. Did you want to rebase and repost packed ring support on top? IIUC it's on par with split ring with...

Hi: This series tries to access virtqueue metadata through kernel virtual address instead of copy_user() friends since they had too much overheads like checks, spec barriers or even hardware feature toggling like SMAP. This is done through setup kernel address through direct mapping and co-opreate VM management with MMU notifiers. Test shows about 23% improvement on TX PPS. TCP_STREAM doesn't see obvious improvement. Thanks Changes from RFC V3: - rebase to net-next - Tweak on the comments Changes from RFC V2: - switch to use direct mapping instead of vmap() - switch to use spinlock +...

Hi: This series tries to access virtqueue metadata through kernel virtual address instead of copy_user() friends since they had too much overheads like checks, spec barriers or even hardware feature toggling like SMAP. This is done through setup kernel address through direct mapping and co-opreate VM management with MMU notifiers. Test shows about 23% improvement on TX PPS. TCP_STREAM doesn't see obvious improvement. Thanks Changes from RFC V3: - rebase to net-next - Tweak on the comments Changes from RFC V2: - switch to use direct mapping instead of vmap() - switch to use spinlock +...

Hello, everyone! Does anyone know how make some symbols have special means in R? For example, we know that "+" in R means the sum of the two operand on its left and right. I want to define some operators in R by myself. Is this possible? Regards! -- Chuanlong Du Department of Statistcis Iowa State University Ames, IA, US 50011 [[alternative HTML version deleted]]

...ock, &msg, >> 1, MSG_DONTWAIT | MSG_TRUNC); >> pr_debug("Discarded rx packet: len %zd\n", sock_len); >> continue; >> } >> ... >> } >> >> This makes it possible to trigger a infinite while..continue loop >> through the co-opreation of two VMs like: >> >> 1) Malicious VM1 allocate 1 byte rx buffer and try to slow down the >> vhost process as much as possible e.g using indirect descriptors or >> other. >> 2) Malicious VM2 generate packets to VM1 as fast as possible >> >> Fixi...

...ock, &msg, >> 1, MSG_DONTWAIT | MSG_TRUNC); >> pr_debug("Discarded rx packet: len %zd\n", sock_len); >> continue; >> } >> ... >> } >> >> This makes it possible to trigger a infinite while..continue loop >> through the co-opreation of two VMs like: >> >> 1) Malicious VM1 allocate 1 byte rx buffer and try to slow down the >> vhost process as much as possible e.g using indirect descriptors or >> other. >> 2) Malicious VM2 generate packets to VM1 as fast as possible >> >> Fixi...

From: Nicholas Bellinger <nab at linux-iscsi.org> Hi folks, This series adds a virtio_queue_valid() for use by virtio-pci code in order to prevent opreations upon uninitialized VQs, that is currently expected to occur during seabios setup of virtio-scsi. This also includes a vhost specific check for uninitialized VQs in vhost_verify_ring_mappings() to avoid this same case. Please review. --nab Michael S. Tsirkin (1): virtio: add API to check t...

From: Nicholas Bellinger <nab at linux-iscsi.org> Hi folks, This series adds a virtio_queue_valid() for use by virtio-pci code in order to prevent opreations upon uninitialized VQs, that is currently expected to occur during seabios setup of virtio-scsi. This also includes a vhost specific check for uninitialized VQs in vhost_verify_ring_mappings() to avoid this same case. Please review. --nab Michael S. Tsirkin (1): virtio: add API to check t...

...iscarded rx packet: len %zd\n", sock_len); > > > > ??????? continue; > > > > ????} > > > > ... > > > > } > > > > > > > > This makes it possible to trigger a infinite while..continue loop > > > > through the co-opreation of two VMs like: > > > > > > > > 1) Malicious VM1 allocate 1 byte rx buffer and try to slow down the > > > > ??? vhost process as much as possible e.g using indirect descriptors or > > > > ??? other. > > > > 2) Malicious VM2 generate p...

...iscarded rx packet: len %zd\n", sock_len); > > > > ??????? continue; > > > > ????} > > > > ... > > > > } > > > > > > > > This makes it possible to trigger a infinite while..continue loop > > > > through the co-opreation of two VMs like: > > > > > > > > 1) Malicious VM1 allocate 1 byte rx buffer and try to slow down the > > > > ??? vhost process as much as possible e.g using indirect descriptors or > > > > ??? other. > > > > 2) Malicious VM2 generate p...

...checked by isSameSize predicate). More over, in very many cases, the operation (e.g. OR) itself affects only the encoding of the operation inside the opcode and of course the description of the effect and assembler syntax e.g. [(store (or (load addr:$dst), GR8:$src), addr:$dst)]. For OR insn the opreation should be or, and for AND insn - obviously and. But operands and operand combinations have the same limitations and descriptions also for many other operations, e.g. XOR, AND, etc. Wouldn't it make sense to provide an easier way to describe it? For example, one would describe operands combin...

...err = sock->ops->recvmsg(sock, &msg, > 1, MSG_DONTWAIT | MSG_TRUNC); > pr_debug("Discarded rx packet: len %zd\n", sock_len); > continue; > } > ... > } > > This makes it possible to trigger a infinite while..continue loop > through the co-opreation of two VMs like: > > 1) Malicious VM1 allocate 1 byte rx buffer and try to slow down the > vhost process as much as possible e.g using indirect descriptors or > other. > 2) Malicious VM2 generate packets to VM1 as fast as possible > > Fixing this by checking against...

...MSG_TRUNC); >>> ??????? pr_debug("Discarded rx packet: len %zd\n", sock_len); >>> ??????? continue; >>> ????} >>> ... >>> } >>> >>> This makes it possible to trigger a infinite while..continue loop >>> through the co-opreation of two VMs like: >>> >>> 1) Malicious VM1 allocate 1 byte rx buffer and try to slow down the >>> ??? vhost process as much as possible e.g using indirect descriptors or >>> ??? other. >>> 2) Malicious VM2 generate packets to VM1 as fast as possible &g...

...rx packet: len %zd\n", sock_len); >>>>> ??????? continue; >>>>> ????} >>>>> ... >>>>> } >>>>> >>>>> This makes it possible to trigger a infinite while..continue loop >>>>> through the co-opreation of two VMs like: >>>>> >>>>> 1) Malicious VM1 allocate 1 byte rx buffer and try to slow down the >>>>> ??? vhost process as much as possible e.g using indirect descriptors or >>>>> ??? other. >>>>> 2) Malicious VM2 gene...