search for: snappi

I scripted the creation of snapshots and it works fine. Now I'd like to run the script as non-root. virsh snapshot-create-as --domain hq-live-v01 \      --name snappy \      --diskspec vda,file=/var/lib/libvirt/images/hq-live-v01.snappy,snapshot=external \      --diskspec vdb,file=/var/lib/libvirt/images/hq-live-storage.snappy,snapshot=external \      --disk-only --quiesce --atomic This

The first four bytes is the length of all data chunks, and the first four bytes of each chunk is the length of compressed chunk data, even when there''s only one chunk, which is the case for inline extents. Signed-off-by: Li Zefan <lizf@cn.fujitsu.com> --- fs/btrfs/snappy.c | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/fs/btrfs/snappy.c

On Wed, Mar 20, 2019 at 15:48:43 -0500, Eric Blake wrote: > On 3/20/19 1:50 PM, Mircea Husz wrote: > > I scripted the creation of snapshots and it works fine. Now I'd like to run the script as non-root. > > > > virsh snapshot-create-as --domain hq-live-v01 \ > >      --name snappy \ > >      --diskspec

On 3/20/19 1:50 PM, Mircea Husz wrote: > I scripted the creation of snapshots and it works fine. Now I'd like to run the script as non-root. > > virsh snapshot-create-as --domain hq-live-v01 \ >      --name snappy \ >      --diskspec vda,file=/var/lib/libvirt/images/hq-live-v01.snappy,snapshot=external \ >      --diskspec

...distance For drag/drop - change the ''release'' animation time to be proportional to the remaining distance the dropped item has to travel. If a user drags the item almost all the way to the final location, the release time should be almost instantaneous (giving the perception of snappiness). Currently the ''release'' time appears fixed, so users feel like they''re waiting unnecessairly for the animation to slowly move the released item a tiny distance. This quickly gets frustrating. *) AutoComplete - avoid blinking, just get the result in the field ASAP...

All I have to say is *wow*. The vectorizer performs *remarkably* better now than it did the last time I benchmarked it. I'm stunned. I measured -O2 and -Os, as well as -march=x86-64 and -march=corei7-avx. My hope with the latter two was to cover both worst-case and best-case in terms of the quality of the vector ISA available. First, binary size growth. This is measured on average across a

Hi, so here it is, LZ4 compression method inside btrfs. The patchset is based on top of current Chris'' for-linus + Andi''s snappy implementation + the fixes from Li Zefan. Passes xfstests and stresstests. I haven''t measured performance on wide range of hardware or workloads, rather wanted to publish the patches before I get distracted again. I''d like to ask

On Jun 24, 2013, at 11:01 AM, Arnold Schwaighofer <aschwaighofer at apple.com> wrote: > Hi, > > I wanted to start a discussion about the following issue since I am not sure about what to do about it: > > The loop-vectorizer has the potential to make code a quite a bit bigger (esp. in cases where we don’t know the loop count or whether pointers alias). > Chandler has

Hello all, I''m attempting to test/tune a mongrel cluster according to the tuning instructions on the mongrel site (using httperf). Anecdotally, the site itself ''feels'' snappy, but testing it with httperf reveals what appears to be terrible throughput. I''m kind of at a loss to describe the results, and was hoping someone could verify that I''m testing

Hi, I wanted to start a discussion about the following issue since I am not sure about what to do about it: The loop-vectorizer has the potential to make code a quite a bit bigger (esp. in cases where we don’t know the loop count or whether pointers alias). Chandler has observed this in snappy where we have a simple memory copying loop (that may overlap). We vectorize this loop and then this

Sorry for the delays here. I am running our benchmark suite and will have data in a day or so. On Jun 13, 2013 9:40 PM, "Nadav Rotem" <nrotem at apple.com> wrote: > Hi, > > Last week I wrote llvm-dev and presented data that shows how enabling the > vectorizer on -Os can improve the performance of many workloads and that it > has negligible effects on code size. I

Hi Everyone, In Xen, is a DomU able to access data in RAM which a previous DomU has stored in the past, but didn''t "zero" it? I understand that this is a problem with physical disks (using phy:/), just wondering if the same stands with RAM Thanks _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Hi Everyone, In Xen, is a DomU able to access data in RAM which a previous DomU has stored in the past, but didn''t "zero" it? I understand that this is a problem with physical disks (using phy:/), just wondering if the same stands with RAM Thanks _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

I know this list is meant for discussion of compiz specifically, but .... 1) I sometimes see compiz spit out "Could not bind pixmap to texture" messages, even though it _appears_ to be working fine. I randomly guess that this is due to me running out of video memory (iirc I have 64mb of vram). Is that possibly a problem? I think Vista and OS X manually manage video

Just to error test my own thinking here, there seems to be the following options for remote graphical access to a running domian vm. Besides the normal network service via a port and a raw console, the options are straight X, VNC, and XN. X - supports a single X window running on a local XServer, tied to a single process on the remote system. No remote desktop VNC - comes in two flavors of

Our Samba server running on CentOS 5.1 (upgraded from 5.0) with Samba 3.0.25b-1.el5_1.4 has been in place for about a year and a half. We had no issues till about 2 months ago. This may have coincided with the upgrade of CentOS 5.0 to 5.1 (which would have brought a new Samba version with it). Anyway, the server will be fine and snappy for a week or so, then out of the blue, nobody can

Hi, Last week I wrote llvm-dev and presented data that shows how enabling the vectorizer on -Os can improve the performance of many workloads and that it has negligible effects on code size. I also added a command line switch to make it easier for people to benchmark the vectorizer using -Os directly from clang without changing LLVM. Has anyone done any benchmarks on -Os + vectorization ?

Greetings all! I have been searching the Site for a function, say "subsets", such that for instance subsets(10) would return a (say) matrix of indices to the 2^10 subsets of N items -- perhaps in the form of 2^10 rows each of which is 10 entries each either TRUE or FALSE. Or 1 or 0. Or ... I can of course write my own, using good old looping technology or similar, but it would be

hi guys, Just wondering if anyone has done any performance testing between kvm and xen on CentOS-5 ( using centos as host and vm in every case ) ? Regards, -- Karanbir Singh London, UK | http://www.karan.org/ | twitter.com/kbsingh ICQ: 2522219 | Yahoo IM: z00dax | Gtalk: z00dax GnuPG Key : http://www.karan.org/publickey.asc

----- Original Message ----- > Hi, > > I wanted to start a discussion about the following issue since I am > not sure about what to do about it: > > The loop-vectorizer has the potential to make code a quite a bit > bigger (esp. in cases where we don’t know the loop count or whether > pointers alias). > Chandler has observed this in snappy where we have a simple