xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Vadim A. Misbakh-Soloviov" <mva@mva.name>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Problem with growing up dom0 memory
Date: Sat, 27 Oct 2012 18:59:50 +0700	[thread overview]
Message-ID: <508BCCB6.7040708@mva.name> (raw)
In-Reply-To: <508BC903.8050104@mva.name>


[-- Attachment #1.1: Type: text/plain, Size: 816 bytes --]

Uhm. It seems, it is 4.1.3 (as you can see from xl info) on 3.5.3-kernel
node, but I have all following issues even on 3.6.3-kernel node with 4.2.0.

P.S.:
By the way, I also has some network speed issues with domUs:

one_node ~mva % scp bkp.txz domU_on_another_node:/home/mva
bkp.txz

                                      3%  592KB 259.7KB/s   0.0KB/s
01:12 ETA^CKilled by signal 2.
one_node ~mva % scp bkp.txz another_node_itself:/home/mva
bkp.txz

                                    100%   19MB   3.8MB/s   6.2MB/s
00:05

almost the same for reversed process (downloading from that places)
it is rt8169 ethernet driver on "one_node", e1000e on "another_node" and
I dunno which driver Xen uses for domUs, but:
domU ~mva % dmesg|grep -i 'Xen.*eth'
Initialising Xen virtual ethernet driver


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 897 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2012-10-27 11:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-27 11:06 Problem with growing up dom0 memory Vadim A. Misbakh-Soloviov
2012-10-27 11:44 ` Vadim A. Misbakh-Soloviov
2012-10-27 11:59   ` Vadim A. Misbakh-Soloviov [this message]
2012-12-19 22:01     ` 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=508BCCB6.7040708@mva.name \
    --to=mva@mva.name \
    --cc=xen-devel@lists.xen.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).