search for: leis

Time stamps are correct and my system time is correct. I am now tried to use Sys.setFileTime() to update time stamps as proposed. This does not help. The windows and debian builds give different reports on the time stamp issue. https://win-builder.r-project.org/incoming_pretest/eurostat_3.2.8_20180920_122655/Windows/00check.log

On Thu, Sep 20, 2018 at 11:46 AM Leo Lahti <leo.lahti at iki.fi> wrote: > > Time stamps are correct and my system time is correct. > > I am now tried to use Sys.setFileTime() to update time stamps as proposed. > This does not help. > > The windows and debian builds give different reports on the time stamp > issue. >

Dear developers, Upon CRAN submission I have bumped into "future file timestamps" warning that I can't solve. I have updated the package as usual, and all checks go through in my system. CRAN reports the following warning however. * checking for future file timestanps ... WARNING Files with future time stamps: DESCRIPTION NAMESPACE README.md The build log is at

Hi experts, I boot the xen4.0.0 with gpxe and boot xen 32 bit works well but when I try boot xen 64 bit, the error happens (XEN)Brought up 16 cpus (XEN) *** LOADING DOMAIN 0 *** (XEN) **************************************** (XEN) Panic on CPU 0: (XEN) crc error (XEN) **************************************** Can you give me a light? Thanks Lei -- "We learn from failure, not from

Hi experts, I boot the xen4.0.0 with gpxe and boot xen 32 bit works well but when I try boot xen 64 bit, the error happens (XEN)Brought up 16 cpus (XEN) *** LOADING DOMAIN 0 *** (XEN) **************************************** (XEN) Panic on CPU 0: (XEN) crc error (XEN) **************************************** Can you give me a light? Thanks Lei -- "We learn from failure, not from

Hi all If I use nfsroot boot the xen dom0, I find it works well if not use initrd-2.6.32.9.img. what does "initrd-2.6.32.9.img" contains? Thanks Lei -- "We learn from failure, not from success!" _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

On Sat, Jun 14, 2014 at 1:29 AM, Ming Lei <ming.lei at canonical.com> wrote: > Firstly this patch supports more than one virtual queues for virtio-blk > device. > > Secondly this patch maps the virtual queue to blk-mq's hardware queue. > > With this approach, both scalability and performance problem can be improved. > > Signed-off-by: Ming Lei <ming.lei at

On Sat, Jun 14, 2014 at 1:29 AM, Ming Lei <ming.lei at canonical.com> wrote: > Firstly this patch supports more than one virtual queues for virtio-blk > device. > > Secondly this patch maps the virtual queue to blk-mq's hardware queue. > > With this approach, both scalability and performance problem can be improved. > > Signed-off-by: Ming Lei <ming.lei at

Hi Lei, Le 31/05/2012 03:44, Lei Mou a écrit : > Problem solved by returning the second result of the ATOMIC_LOAD_OR node... You got the chain instead of the loaded value. IMHO, a better solution would have been to add a Pat<> rule to match truncstores and expand them into target store/load/and/or. Pat : <(truncstore16 GPR:$val, MEM:$mem), (store MEM:$mem, (or

Hello, I'm trying to superimpose a line plot onto a histogram but I'm not having any luck. I've attached the dataset. What I did was: > hist(data,freq=F) Now I'm trying to superimpose the following points with a line connecting them onto the histogram: x y 100 0.535665393824959 200 0.212744329736556 300 0.0844933242968584 400 0.0335572838043417 500

Firstly, it isn't necessary to hold lock of vblk->vq_lock when notifying hypervisor about queued I/O. Secondly, virtqueue_notify() will cause world switch and it may take long time on some hypervisors(such as, qemu-arm), so it isn't good to hold the lock and block other vCPUs. On arm64 quad core VM(qemu-kvm), the patch can increase I/O performance a lot with VIRTIO_RING_F_EVENT_IDX

Firstly, it isn't necessary to hold lock of vblk->vq_lock when notifying hypervisor about queued I/O. Secondly, virtqueue_notify() will cause world switch and it may take long time on some hypervisors(such as, qemu-arm), so it isn't good to hold the lock and block other vCPUs. On arm64 quad core VM(qemu-kvm), the patch can increase I/O performance a lot with VIRTIO_RING_F_EVENT_IDX

On Tue, Feb 18, 2020 at 8:35 PM Halil Pasic <pasic at linux.ibm.com> wrote: > > On Tue, 18 Feb 2020 10:21:18 +0800 > Ming Lei <tom.leiming at gmail.com> wrote: > > > On Thu, Feb 13, 2020 at 8:38 PM Halil Pasic <pasic at linux.ibm.com> wrote: > > > > > > Since nobody else is going to restart our hw_queue for us, the > > >

Hi all, I'm learning the PTX backend and confused by the following problem. In the constructor of PTXFrameLowering, StackAlignment and LocalAreaOffset are assigned 2 and -2, respectively. Since PTX has neither stack frame nor stack pointer, why StackAlignment and LocalAreaOffset are needed and where does 2 and -2 come from? Any explanation is appreciated. Thank you in advance! Yours

Hi experts,'' I build xen on my 64 bit redhat with "make xen", I got the image xen-4.0.0.gz then $gunzip xen-4.0.0.gz $file xen-4.0.0 it tells me it''s 32 bit,but I saw it link the 64 bit lib Thanks Lei -- "We learn from failure, not from success!" _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi experts,'' I build xen on my 64 bit redhat with "make xen", I got the image xen-4.0.0.gz then $gunzip xen-4.0.0.gz $file xen-4.0.0 it tells me it''s 32 bit,but I saw it link the 64 bit lib Thanks Lei -- "We learn from failure, not from success!" _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi, Our target only has native support for i32 and f32 types. For data types smaller than these, I have to custom lowering truncating store using two atomic load instruction (which have the same semantics as ISD::ATOMIC_LOAD_AND and ATOMIC_LOAD_OR, respectively). I run into a problem during the legalization process, where the legalizer complains that ISD::STORE and ISD::ATOMIC_LOAD_OR (generated

Problem solved by returning the second result of the ATOMIC_LOAD_OR node... On Wed, May 30, 2012 at 9:38 PM, Lei Mou <lei.mou.uu at gmail.com> wrote: > Hi, > > Our target only has native support for i32 and f32 types. For data > types smaller than these, I have to custom lowering truncating store > using two atomic load instruction (which have the same semantics as >

> Message: 4 > Date: Sun, 27 Jun 2004 03:18:43 -0400 > From: Lei Liu <liulei at l.imap.itd.umich.edu> > Subject: [R] help in R calling C function > To: r-help at stat.math.ethz.ch > Message-ID: <5.1.0.14.1.20040627030746.014936b8 at l.imap.itd.umich.edu> > Content-Type: text/plain; charset="us-ascii"; format=flowed > > Hi there, > > I want

Hi, This patches try to support multi virtual queues(multi-vq) in one virtio-blk device, and maps each virtual queue(vq) to blk-mq's hardware queue. With this approach, both scalability and performance problems on virtio-blk device get improved. For verifying the improvement, I implements virtio-blk multi-vq over qemu's dataplane feature, and both handling host notification from each vq