similar to: hong_en@solenw.org

-- null -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/virtualization/attachments/20180224/404443b5/attachment-0001.html>

hong_en at solenw.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/virtualization/attachments/20180207/f76ec3e0/attachment.html>

solenwin2.zendesk.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/virtualization/attachments/20180213/69692556/attachment.html>

Hi sir solenwin2.zendesk.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/virtualization/attachments/20180307/253fa2ad/attachment.html>

The original message was received at Thu, 28 Dec 2006 13:07:05 +0200 from 190.177.71.174 ----- The following addresses had permanent fatal errors ----- virtualization@lists.osdl.org

----- Forwarded message from Chet Ensign <chet.ensign at oasis-open.org> ----- Date: Fri, 28 Mar 2014 17:54:16 -0400 From: Chet Ensign <chet.ensign at oasis-open.org> To: tc-announce at lists.oasis-open.org, members at lists.oasis-open.org, virtio at lists.oasis-open.org, virtio-comment at lists.oasis-open.org Subject: [members] 15-day Public Review for Virtual I/O Device (VIRTIO)

We are about to launch our public beta content management system. We wanted to address our work groups first to give you the opportunity to have first access and update content in the new CMS. Log into https://beta.linuxfoundation.org/collaborate/workgroups with your LF account. The same account you used for wiki. Click on your respective group and then click Join or Request Membership from the

On Fri, 14 Sep 2018, Florian Weimer wrote: > On 09/14/2018 03:05 PM, Thomas Gleixner wrote: > > On Fri, 14 Sep 2018, Florian Weimer wrote: > > > > > On 09/14/2018 02:50 PM, Thomas Gleixner wrote: > > > > Matt attempted to add CLOCK_TAI support to the VDSO clock_gettime() > > > > implementation, which extended the clockid switch case and added yet

On Sat, Aug 03, 2019 at 09:14:00PM -0300, Jason Gunthorpe wrote: > On Sat, Aug 03, 2019 at 05:36:13PM -0400, Michael S. Tsirkin wrote: > > On Fri, Aug 02, 2019 at 02:24:18PM -0300, Jason Gunthorpe wrote: > > > On Fri, Aug 02, 2019 at 10:27:21AM -0400, Michael S. Tsirkin wrote: > > > > On Fri, Aug 02, 2019 at 09:46:13AM -0300, Jason Gunthorpe wrote: > > > >

On Fri, Aug 02, 2019 at 10:27:21AM -0400, Michael S. Tsirkin wrote: > On Fri, Aug 02, 2019 at 09:46:13AM -0300, Jason Gunthorpe wrote: > > On Fri, Aug 02, 2019 at 05:40:07PM +0800, Jason Wang wrote: > > > > This must be a proper barrier, like a spinlock, mutex, or > > > > synchronize_rcu. > > > > > > > > > I start with synchronize_rcu()

On Fri, Aug 02, 2019 at 02:24:18PM -0300, Jason Gunthorpe wrote: > On Fri, Aug 02, 2019 at 10:27:21AM -0400, Michael S. Tsirkin wrote: > > On Fri, Aug 02, 2019 at 09:46:13AM -0300, Jason Gunthorpe wrote: > > > On Fri, Aug 02, 2019 at 05:40:07PM +0800, Jason Wang wrote: > > > > > This must be a proper barrier, like a spinlock, mutex, or > > > > >

On Sat, Aug 03, 2019 at 05:36:13PM -0400, Michael S. Tsirkin wrote: > On Fri, Aug 02, 2019 at 02:24:18PM -0300, Jason Gunthorpe wrote: > > On Fri, Aug 02, 2019 at 10:27:21AM -0400, Michael S. Tsirkin wrote: > > > On Fri, Aug 02, 2019 at 09:46:13AM -0300, Jason Gunthorpe wrote: > > > > On Fri, Aug 02, 2019 at 05:40:07PM +0800, Jason Wang wrote: > > > > >

The original message was received at Thu, 28 Dec 2006 13:07:05 +0200 from 190.177.71.174 ----- The following addresses had permanent fatal errors ----- virtualization@lists.osdl.org

If you do this whats the point of the id? Just use descriptor offset like virtio 0 did. On Sun, Oct 29, 2017 at 09:05:01AM +0000, Ilya Lesokhin wrote: > My point was that if the driver is not required to change the IDs, > it can initialized the ID's in all the descriptors when the ring is created > and never write the ID field again. > > A simple allocator for the IDs can

On Mon, Oct 27, 2014 at 01:15:53PM -0400, Waiman Long wrote: > On 10/24/2014 06:04 PM, Peter Zijlstra wrote: > >On Fri, Oct 24, 2014 at 04:53:27PM -0400, Waiman Long wrote: > >>The additional register pressure may just cause a few more register moves > >>which should be negligible in the overall performance . The additional > >>icache pressure, however, may have

* Wei Wang (wei.w.wang at intel.com) wrote: > On 07/23/2018 10:36 PM, Dr. David Alan Gilbert wrote: > > * Michael S. Tsirkin (mst at redhat.com) wrote: > > > On Fri, Jul 20, 2018 at 04:33:00PM +0800, Wei Wang wrote: > > > > This patch series is separated from the previous "Virtio-balloon > > > > Enhancement" series. The new feature,

On Sun, Oct 08, 2017 at 06:16:44AM +0000, Ilya Lesokhin wrote: > > > -----Original Message----- > > > From: virtualization-bounces at lists.linux-foundation.org > > > [mailto:virtualization-bounces at lists.linux-foundation.org] On Behalf > > > Of Michael S. Tsirkin > > > > > > This is an update from v2 version. > >> ... > > >

This gives small but noticeable rx performance improvement (2-3%) and will allow exploiting future napi improvement. Signed-off-by: Paolo Abeni <pabeni at redhat.com> --- drivers/net/virtio_net.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c index fb0eae4..49d84e5 100644 --- a/drivers/net/virtio_net.c +++

On Thu, Nov 03, 2011 at 08:49:31AM -0500, Anthony Liguori wrote: > On 11/03/2011 08:45 AM, Avi Kivity wrote: > >On 11/03/2011 03:38 PM, Anthony Liguori wrote: > >>> > >>>>We could use a better agreement on the processor for making virtio > >>>>changes. Should it go (1) virtio spec (2) kernel (3) qemu, or should > >>>>it go (2), (1),

On Mon, Apr 09, 2018 at 05:44:36AM +0300, Michael S. Tsirkin wrote: > On Mon, Apr 09, 2018 at 10:37:45AM +0800, Stefan Hajnoczi wrote: > > On Sat, Apr 7, 2018 at 3:02 AM, syzbot > > <syzbot+65a84dde0214b0387ccd at syzkaller.appspotmail.com> wrote: > > > syzbot hit the following crash on upstream commit > > > 38c23685b273cfb4ccf31a199feccce3bdcb5d83 (Fri Apr 6