I've changed the status of this case to 'waiting need spec' as the
project team are working on changing the output from vmstat with
the new -h option to remove the ambiguity within it.
3. glenn.skinner >>
//
Date: Wed, 21 May 2008 09:34:40 -0700
From: Eric Sultan
Subject: Re: vmstat(1m) humanisation [PSARC/2008/329 FastTrack
timeout 05/16/2008]
AFAIK, IEEE standards use lower-case 'k' for kilo. This isn't, of
course, to say
Hello,
Please find answers below.
John.Plocher >>
<===snip>
In particular, the phrase ...
skip fields in the order right to left. On the omission of
fields in random order, the alignment of the header is not
guaranteed.
... sounds like you are defining a "skip list
Hello,
Glenn Fowler >>
<--snip--->
in this proposal is 50K == 50*1000 or is it 50Ki == 50*1024?
the same question for { Mi Gi }
also, if "and so on" means Ti ... then maybe those should be spelled out
---
ast has a function fmtscale(3) that handles this issue in one spot
relevanc
Hello,
Jeremy Harris >>
> K == kilo
> > M == Mega
> > G == Giga
>
> > Isn't the usual signifier for kilo a lower-case 'k'?
>
No. I have only come across a upper-case 'K' for kilo.
Example : df -hl
[mp204432 at drosera:23:13:57]/export/users/mp204432:df -hl swap
F
Hello,
Please find the answers below.
1.a.
I certainly don't find that any more readable.
The units are confusing too. For pageins, is that pages, kilobytes, or k/s?
The sizes of fields which were output in kilobytes are only scaled
to a human readable format, for example,
44.1G 9.9M 2T 199K
On Wed, May 21, 2008 at 07:27:30PM +0530, manjula pc - Sun Microsystems -
Bangalore India wrote:
> ** The fields can be omitted in any order.
I think you mean "emitted".
regards
john
AFAIK, IEEE standards use lower-case 'k' for kilo. This isn't, of
course, to say that folks haven't been ignoring the standard or perhaps
not have known it.
Within Sun, the Editorial Style Guide conforms to established standards
and specifies the use of lower-case 'k' for kilo.
Regards,
-
I believe you still need to address IEEE 1541 units
http://en.wikipedia.org/wiki/IEEE_1541
i.e.,
5.0k 124M# divide by 1000
4.9Ki 118Mi # divide by 1024
this will disambiguate displayed values and may also
help to clean up the documentation
-- Glenn Fowler -- AT&T Resear
Hello,
Thanks for all the comments.
Have been working on all the concerns and will get back by tomorrow.
Best Regards,
Manjula
Peter Dennis - Sustaining Engineer wrote:
> Due to the various comments on this case I have set a timer for it:
> 23-May-2008.
>
> The project team will be responding
Due to the various comments on this case I have set a timer for it:
23-May-2008.
The project team will be responding to the questions asked
(please keep manjula.pc at sun.com on the cc list).
Thanks
Pete
ast has a function fmtscale(3) that handles this issue in one spot
relevance to solaris is that ksh93 exposes this function via
libast/sfprintf(3) and finally its builtin printf(1)
from ksh93 try
printf $'%#d %#i\n' 5000 5000 123456789 123456789
and it should produce
5.0k 4.9Ki
On May 18, 2008, at 2:05 PM, Joseph Kowalski wrote:
> / /I think all (if not most) questions around the spelling of the
> various magnitudes can be found in:
>
>PSARC/2001/183 df -h and -H options
>
> If there is an old case, or a newer one which alters this precedent,
> I'm
> not aware of
Dale Ghent wrote:
> On May 18, 2008, at 2:05 PM, Joseph Kowalski wrote:
>
>> / /I think all (if not most) questions around the spelling of the
>> various magnitudes can be found in:
>>
>>PSARC/2001/183 df -h and -H options
>>
>> If there is an old case, or a newer one which alters this preced
Jeremy Harris wrote:
> Peter Dennis wrote:
>> K == kilo
>> M == Mega
>> G == Giga
>
> Isn't the usual signifier for kilo a lower-case 'k'?
>
> - Jeremy Harris
/ /I think all (if not most) questions around the spelling of the
various magnitudes can be found in:
PSARC/2
Peter Dennis wrote:
> K == kilo
> M == Mega
> G == Giga
Isn't the usual signifier for kilo a lower-case 'k'?
- Jeremy Harris
>The first is the "h" option which will produce output in
>human readable format, thereby making it easily readable
>to the user,
>
> Example "h" option output:
>
> vmstat
> kthr memorypagedisk faults cpu
> r b w swap free re m
in this proposal is 50K == 50*1000 or is it 50Ki == 50*1024?
the same question for { Mi Gi }
also, if "and so on" means Ti ... then maybe those should be spelled out
-- Glenn Fowler -- AT&T Research, Florham Park NJ --
Peter Dennis wrote:
> The second is the "o" option which will allow the user to
> skip fields in the order right to left. On the omission of
> fields in random order, the alignment of the header is not
> guaranteed. At all times, all fields may not be of interest
> to
I'm submitting this case for Manjula Pc. The requested release taxonomy
is Patch.
I believe this qualifies for automatic approval given the precdent set
by PSARC/2006/179. If anyone disagrees I'll set the normal one week timer.
Suggested man changes are in the materials directory.
Template Vers
20 matches
Mail list logo
