From: George Shuklin <george.shuklin@gmail.com>
To: "Fajar A. Nugraha" <list@fajar.net>
Cc: xen-devel@lists.xensource.com
Subject: Re: a ton of kernel issues
Date: Wed, 14 Dec 2011 22:40:08 +0400 [thread overview]
Message-ID: <4EE8ED88.8060107@gmail.com> (raw)
In-Reply-To: <CAG1y0sfbgrCsgLgF5-PZ24vzznwTjrPHkWMwAJO7qKYnVT+ODg@mail.gmail.com>
On 14.12.2011 11:47, Fajar A. Nugraha wrote:
>> Well... For us it make HUGE difference. We running cloud with very precise
>> accounting of fast automaric memory allocation for customer's domains and
>> we account them for ... em... KiB*hr value, so if we account domains based
>> on xc.get_domain_memkb value and customers saw difference between TotalMem
>> and our values this will make them feel like we cheating. We not greedy and
>> ready to 'cut' our mem_kb value to their TotalMem, but I hasn't found any
>> formula for that (calculate TotalMem from static-max and dom_kb values) and
>> I can't trust any data from customer's domains (except request for memory we
>> accept, serve and happily take money for 'more memory').
>>
>> It sounds ridiculous, but we avoiding pv_ops kernels usage due that little
>> ~50Mb steal. We stuck with -xen kernels (forward porting from SUSE and
>> native CentOS 2.6.18-xen). I don't know what we will do in the future, but
>> right now PV-ops is not good...
> Why not just explain what really happened in a noob-friendly language?
>
> For example, when buying a computer with built-in graphic card,
> MemTotal is always lower than the ammount of memory actually
> installed. Yet a simple explanation "some of the memory is used by the
> built-in graphic card" is enough, without having to go into details of
> what is the formula to calculate how much memory actualy used.
>
Well, this is fine if we provide customers normal 'VDS-like' virtual
machines. You getting 256MiB, some of it is used by kernel and not
displayed as TotalMem. But we provide vm with ellastic memory (like
256MiB - 8GiB) with promise 'we will serve you enough memory to your
applications and you will pay only for allocated memory for your VM'.
User expects we give him + 2GiB for 2 min and we charge him for
2*2/60=0.066 GiB*hr. With -xen kernels they got exactly they paid (at
least, with TotalMem value). If we saying them 'here something you don't
understand' this will cause some doubts.
next prev parent reply other threads:[~2011-12-14 18:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 21:44 a ton of kernel issues Tim Evers
2011-12-12 21:56 ` Konrad Rzeszutek Wilk
2011-12-14 9:00 ` Tim Evers
2011-12-15 1:25 ` Konrad Rzeszutek Wilk
2011-12-13 9:09 ` George Shuklin
2011-12-13 10:19 ` Alessandro Salvatori
2011-12-13 10:36 ` George Shuklin
2011-12-13 13:17 ` David Vrabel
2011-12-13 13:37 ` Ian Campbell
2011-12-13 20:59 ` George Shuklin
2011-12-13 22:30 ` Ian Campbell
2011-12-13 22:53 ` George Shuklin
2011-12-14 7:25 ` Ian Campbell
2011-12-14 12:16 ` Ian Campbell
2011-12-14 12:21 ` David Vrabel
2011-12-14 13:11 ` Jan Beulich
2011-12-14 13:48 ` Ian Campbell
2011-12-14 17:44 ` Konrad Rzeszutek Wilk
2011-12-15 12:45 ` George Shuklin
2011-12-15 16:26 ` Konrad Rzeszutek Wilk
2011-12-13 21:05 ` George Shuklin
2011-12-13 21:45 ` Konrad Rzeszutek Wilk
2011-12-14 12:28 ` David Vrabel
2011-12-14 16:57 ` Konrad Rzeszutek Wilk
2011-12-14 7:47 ` Fajar A. Nugraha
2011-12-14 18:40 ` George Shuklin [this message]
2011-12-13 14:18 ` Konrad Rzeszutek Wilk
2011-12-13 21:10 ` George Shuklin
2011-12-13 21:38 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EE8ED88.8060107@gmail.com \
--to=george.shuklin@gmail.com \
--cc=list@fajar.net \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.