search for: opreations

...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]]

On Thu, May 30, 2019 at 11:07:30AM -0700, David Miller wrote: > From: Jason Wang <jasowang at redhat.com> > Date: Fri, 24 May 2019 04:12:12 -0400 > > > 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 > >

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

When the rx buffer is too small for a packet, we will discard the vq descriptor and retry it for the next packet: while ((sock_len = vhost_net_rx_peek_head_len(net, sock->sk, &busyloop_intr))) { ... /* On overrun, truncate and discard */ if (unlikely(headcount > UIO_MAXIOV)) { iov_iter_init(&msg.msg_iter, READ, vq->iov, 1, 1); err = sock->ops->recvmsg(sock,

When the rx buffer is too small for a packet, we will discard the vq descriptor and retry it for the next packet: while ((sock_len = vhost_net_rx_peek_head_len(net, sock->sk, &busyloop_intr))) { ... /* On overrun, truncate and discard */ if (unlikely(headcount > UIO_MAXIOV)) { iov_iter_init(&msg.msg_iter, READ, vq->iov, 1, 1); err = sock->ops->recvmsg(sock,

From: Jason Wang <jasowang at redhat.com> Date: Fri, 24 May 2019 04:12:12 -0400 > 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

On Fri, May 24, 2019 at 04:12:12AM -0400, Jason Wang wrote: > 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

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

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

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]]

On 2019/4/26 ??1:52, Michael S. Tsirkin wrote: > On Thu, Apr 25, 2019 at 03:33:19AM -0400, Jason Wang wrote: >> When the rx buffer is too small for a packet, we will discard the vq >> descriptor and retry it for the next packet: >> >> while ((sock_len = vhost_net_rx_peek_head_len(net, sock->sk, >> &busyloop_intr))) { >> ... >> /* On

On 2019/4/26 ??1:52, Michael S. Tsirkin wrote: > On Thu, Apr 25, 2019 at 03:33:19AM -0400, Jason Wang wrote: >> When the rx buffer is too small for a packet, we will discard the vq >> descriptor and retry it for the next packet: >> >> while ((sock_len = vhost_net_rx_peek_head_len(net, sock->sk, >> &busyloop_intr))) { >> ... >> /* On

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 that...

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 that...

On Sun, May 05, 2019 at 12:20:24PM +0800, Jason Wang wrote: > > On 2019/4/26 ??3:35, Jason Wang wrote: > > > > On 2019/4/26 ??1:52, Michael S. Tsirkin wrote: > > > On Thu, Apr 25, 2019 at 03:33:19AM -0400, Jason Wang wrote: > > > > When the rx buffer is too small for a packet, we will discard the vq > > > > descriptor and retry it for the next

On Sun, May 05, 2019 at 12:20:24PM +0800, Jason Wang wrote: > > On 2019/4/26 ??3:35, Jason Wang wrote: > > > > On 2019/4/26 ??1:52, Michael S. Tsirkin wrote: > > > On Thu, Apr 25, 2019 at 03:33:19AM -0400, Jason Wang wrote: > > > > When the rx buffer is too small for a packet, we will discard the vq > > > > descriptor and retry it for the next

Hi, I'm trying to implement a new backend for an embedded CISC processor. Therefore I thought that it makes sense to take X86 target as a basis, to save some time. But when I look into the X86InstrInfo.td, I have a very strong feeling that it is one of the most complex instruction set descriptions compared to other targets. I can imagine that this is due to the complexity of X86's

On Thu, Apr 25, 2019 at 03:33:19AM -0400, Jason Wang wrote: > When the rx buffer is too small for a packet, we will discard the vq > descriptor and retry it for the next packet: > > while ((sock_len = vhost_net_rx_peek_head_len(net, sock->sk, > &busyloop_intr))) { > ... > /* On overrun, truncate and discard */ > if (unlikely(headcount > UIO_MAXIOV))

On 2019/4/26 ??3:35, Jason Wang wrote: > > On 2019/4/26 ??1:52, Michael S. Tsirkin wrote: >> On Thu, Apr 25, 2019 at 03:33:19AM -0400, Jason Wang wrote: >>> When the rx buffer is too small for a packet, we will discard the vq >>> descriptor and retry it for the next packet: >>> >>> while ((sock_len = vhost_net_rx_peek_head_len(net, sock->sk,

On 2019/5/13 ??1:10, Michael S. Tsirkin wrote: > On Sun, May 05, 2019 at 12:20:24PM +0800, Jason Wang wrote: >> On 2019/4/26 ??3:35, Jason Wang wrote: >>> On 2019/4/26 ??1:52, Michael S. Tsirkin wrote: >>>> On Thu, Apr 25, 2019 at 03:33:19AM -0400, Jason Wang wrote: >>>>> When the rx buffer is too small for a packet, we will discard the vq