Displaying 20 results from an estimated 116 matches for "miscalculates".
Did you mean:
miscalculated
2005 May 04
4
HTB rate miscalculation
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
2005 Dec 16
1
Miscalculation in a comment in dsl_dataset.h
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
2011 Jan 04
0
Queues, priorities and (miscalculated) holdtimes
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
2015 Jan 07
0
[PATCH] vhost/net: length miscalculation
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:
2015 Jan 07
0
[PATCH] vhost/net: length miscalculation
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:
2015 Jan 07
3
[PATCH] vhost/net: length miscalculation
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>
2015 Jan 07
3
[PATCH] vhost/net: length miscalculation
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>
2017 Apr 17
2
Patch: Fix isohybrid.c tool under Windows platforms
> Hi,
>
> Colin Finck wrote:
> > 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 opening the file in binary mode with the "b" flag.
>
> This is a very reasonable
2010 Aug 03
1
snapshot space - miscalculation?
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
2012 Jun 24
2
Power calculation using pwr.t.test()
Dear R experts,
I have conducted a power calculation in order to estimate the number of
subjects needed to detect an effect size of d=0.28 (cohen's d) for a
difference between 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
2017 Apr 10
3
Patch: Fix isohybrid.c tool under Windows platforms
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
2017 Feb 02
2
Specify special cases of delay slots in the back end
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
2008 Aug 03
3
Questions on cpu frequency scaling AMD vs. Intel
...quency 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 whether this CPU should be
supported in full and frequency scaling working? (I'm not sure, but I
think it may have actually worked when it was running in a different
motherboard.)
Kai
--
Kai...
2017 Apr 17
0
Patch: Fix isohybrid.c tool under Windows platforms
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
2006 Sep 18
1
Legend frame error (PR#9236)
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(seq(0,50), 10)
par(mfcol=c(2,1))
2015 Jan 08
0
[PULL] vhost: cleanups and fixes
The following changes since commit b1940cd21c0f4abdce101253e860feff547291b0:
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)
2015 Jan 08
0
[PULL] vhost: cleanups and fixes
The following changes since commit b1940cd21c0f4abdce101253e860feff547291b0:
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)
2002 May 07
1
More on ties with rank()
I am grateful to Prof. Ripley for his explanation. Indeed, rounding explains
it all.
I take the difference between two vectors and call it "z"
method.a <- c(6.3, 6.3, 3.5, 5.1, 5.5, 7.7, 6.3, 2.8, 3.4, 5.7, 5.6, 6.2,
6.6,
7.7, 7.4, 5.6, 6.3, 8.4, 5.6, 4.8, 4.3, 4.2, 3.3,
3.8, 5.7, 4.1)
method.b <- c(5.2, 6.6, 2.3, 4.4, 4.1, 6.4, 5.4, 2.3, 3.2, 5.2, 4.9,
2006 Mar 13
1
[R] dotchart: Gap between text and chart (PR#8681)
...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 not a...
2004 Nov 11
1
Ogg spec
Hi,
I'm currently trying to implement the Ogg specification in pure Java
from scratch. (I know, something like that does exist, but that's a rewrite
from C, at least that's my impression).
I'm a bit confused with the number of lacing values/segments in a page,
and the maximum length a page can have. The specification says, that
there can be 255 segments in a page, 255 bytes each