search for: miscalcul

Hi, I''ve migrated my tc configuration from CBQ to HTB. One problem appeared. Htb seems to miscalculate the bandwidth for classes with greater rates. For rates below 2Mbit there is almost no difference between the configured and the measured rate. For large ones the problem starts. My root class has 10Mbit rate and when the interface has heavy trafic the measured bandwidth coudn''t...

Line 71 of http://cvs.opensolaris.org/source/xref/on/usr/src/uts/common/fs/zfs/sys/dsl_dataset.h#dsl_dataset_phys says uint64_t ds_pad[8]; /* pad out to 256 bytes for good measure */ But that padding actually increases dsl_dataset_phys to 320 bytes total; the structure is already 256 bytes without the padding. This message posted from opensolaris.org

Anyone ever noticed that the reported holdtime is wrong when there are different priorities? Also talktime is 0, but for the moment I don't care. "queue show test" reports: test has 23 calls (max unlimited) in 'ringall' strategy (193s holdtime, 0s talktime) [...] Callers: 1. Local/351 at default-8828;2 (wait: 3:32, prio: 15) 2. Local/351 at default-8361;2

Hello. On 01/07/2015 11:55 AM, Michael S. Tsirkin wrote: > commit 8b38694a2dc8b18374310df50174f1e4376d6824 > vhost/net: virtio 1.0 byte swap > had this chunk: > - heads[headcount - 1].len += datalen; > + heads[headcount - 1].len = cpu_to_vhost32(vq, len - datalen); > This adds datalen with the wrong sign, causing guest panics. > Fixes:

Hello. On 01/07/2015 11:55 AM, Michael S. Tsirkin wrote: > commit 8b38694a2dc8b18374310df50174f1e4376d6824 > vhost/net: virtio 1.0 byte swap > had this chunk: > - heads[headcount - 1].len += datalen; > + heads[headcount - 1].len = cpu_to_vhost32(vq, len - datalen); > This adds datalen with the wrong sign, causing guest panics. > Fixes:

commit 8b38694a2dc8b18374310df50174f1e4376d6824 vhost/net: virtio 1.0 byte swap had this chunk: - heads[headcount - 1].len += datalen; + heads[headcount - 1].len = cpu_to_vhost32(vq, len - datalen); This adds datalen with the wrong sign, causing guest panics. Fixes: 8b38694a2dc8b18374310df50174f1e4376d6824 Reported-by: Alex Williamson <alex.williamson at redhat.com>

commit 8b38694a2dc8b18374310df50174f1e4376d6824 vhost/net: virtio 1.0 byte swap had this chunk: - heads[headcount - 1].len += datalen; + heads[headcount - 1].len = cpu_to_vhost32(vq, len - datalen); This adds datalen with the wrong sign, causing guest panics. Fixes: 8b38694a2dc8b18374310df50174f1e4376d6824 Reported-by: Alex Williamson <alex.williamson at redhat.com>

...on descendants of > Unix and DOS, then one should in any case add "b" to the fopen(3) mode > string. > > Not only MBR writing but also reading of the Primary Volume Descriptor > and of the El Torito catalog by isohybrid.c are currently prone to > unwanted CR-insertion. Miscalculations can be caused by this. Is there anything that can be done in order to reduce such chances of miscalculation and/or unwanted insertion of (CR) characters? > > The fopen() call for reading external MBR code (option -m) already has "b". > > The old perl code contai...

zfs get all claims that i have 523G used by snapshot. i want to get rid of it. but when i look at the space used by each snapshot i can''t find the one that can occupy so much space daten/backups used 959G - daten/backups

...tween two independent groups (alpha level should be 0.05 and the effect should be detected with 80% probability). The results from the code below indicates that I would need n=400 subjects (200 in each group). This is seems so incredibly high that I mistrust my results & wanted to ask whether I miscalculated n? library(pwr) pwr.t.test(d=0.28,sig.level=0.05,power=0.8,type="two.sample",alternative="two.sided") Many thanks for you help! Jokel [[alternative HTML version deleted]]

Hi all, As part of a bigger effort to port the ISOLINUX hybrid mode to ReactOS, I've encountered a bug in isohybrid under Windows platforms. Attached comes a patch to fix it. Precisely, if isohybrid currently finds a 0x0A (LF) byte in the MBR code (which exists in the strings), it adds a 0x0D (CR) before, thereby shifting the MBR bytes to the right and making it invalid. This can be fixed by

Hello. I see there is little information on specifying instructions with delay slots. So could you please tell me how can I insert NOPs (BEFORE or after an instruction) or how to make an aware instruction scheduler in order to avoid miscalculations due to the delay slot effect? More exactly, I have the following constraints on my (SIMD) processor: - certain stores or loads, must be executed 1 cycle after the instruction generating their input operands ends. For example, if I have: R1 = R2 + R3 LS[R10]...

...d by CentOS 5.2 and the current frequency was shown as 800000 (instead of 2500000), although it was running in full speed. The latest kernel corrected this. It's still unknown, but the frequency is now calculated correctly and thus frequency scaling works now (it didn't work when it was miscalculating at 800000). On the other hand, I have an older low-voltage AMD CPU (probably about 2 years on the market) that is recognized as X2 3800+ but frequency scaling fails because it miscalculates the current speed to 800 MHz as well. Is there anything I can do about that? Where could I check whe...

Hi, i wrote: > > Not only MBR writing but also reading of the Primary Volume Descriptor > > and of the El Torito catalog by isohybrid.c are currently prone to > > unwanted CR-insertion. Miscalculations can be caused by this. I have to correct myself: Carriage Return characters (byte value 13 = 0x0d) are not at risk to be inserted, but rather to be removed if they happen to be followed by a New Line character (value 10 = 0x0a). So for example the block address bytes 0d 0a 00 00 (= 2573 dec...

Hello, The frame drawn around the legend appears to miscalculate when the x-axis decreases rather than increases. Pasted below is a simple testcase. When the x-axis decreases, the width of the legend frame appears to be calculated based on the length of the first item, rather than the maximum length of all items. Thanks, -TAG Todd A. Gibson line1=dpois(se...

...940cd21c0f4abdce101253e860feff547291b0: Linux 3.19-rc3 (2015-01-05 17:05:20 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus for you to fetch changes up to 99975cc6ada0d5f2675e83abecae05aba5f437d2: vhost/net: length miscalculation (2015-01-07 12:22:00 +0200) ---------------------------------------------------------------- virtio, vhost fixes for 3.19 This fixes a couple of bugs triggered by hot-unplug of virtio devices, as well as a regression in vhost-net. Cc: Rusty Russell <rusty at rustcorp.com.au> Signed-of...

...940cd21c0f4abdce101253e860feff547291b0: Linux 3.19-rc3 (2015-01-05 17:05:20 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus for you to fetch changes up to 99975cc6ada0d5f2675e83abecae05aba5f437d2: vhost/net: length miscalculation (2015-01-07 12:22:00 +0200) ---------------------------------------------------------------- virtio, vhost fixes for 3.19 This fixes a couple of bugs triggered by hot-unplug of virtio devices, as well as a regression in vhost-net. Cc: Rusty Russell <rusty at rustcorp.com.au> Signed-of...

...999999, 0.699999999999999, 0.9, 0.9, 1.1, 1.1, 1.2, 1.3, 1.4) > rank(k) [1] 2.5 2.5 2.5 2.5 5.5 5.5 8.0 8.0 8.0 10.0 12.0 12.0 12.0 15.0 15.0 [16] 15.0 17.5 17.5 19.5 19.5 21.0 22.0 23.0 > But it strikes me as odd, that such an innocent calculation could lead to such a significant miscalculation based on rounding error. Thanks, ANDREW -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body"...

...tung und > Kultur", > "Bildungswesen", "Beherbergungs und Gaststaettendienstleistungen", > "Andere Waren und Dienstleistungen")) > > dotchart(sort(a)) > dotchart(sort(a),cex=0.7) I've determined that this is a bug in dotchart. It miscalculates the height of a line of text in the right margin, using lheight <- strheight("M", "inch") which doesn't give the right answer. You get the correct answer in this case by putting lheight <- par("mai")[2]/par("mar")[2] but that's no...

...ut later it states the maximum size of a page is 65307 which is strangely 255*256+27. Now where does that extra segment come from? I tried to read every FA I've found, and the mail archives, but couldn't figure this one out. Either I don't "get" something, or that's simply miscalculated. Similar minor issue: How does one describe a 'nil' page. The reference implementation libogg-1.1.1 seems to write a 'page_segment' of 0, and no lacing values, but the rfc states, that a 'nil' page contains only a lacing value of 0 (so a page_segment value of 1). Of cour...