* xen 3 dom0 eats memory
@ 2006-01-04 13:43 Patrick Scharrenberg
2006-01-04 14:35 ` Keir Fraser
0 siblings, 1 reply; 12+ messages in thread
From: Patrick Scharrenberg @ 2006-01-04 13:43 UTC (permalink / raw)
To: Xen-devel
Hi!
Since my upgrade from xen 2-testing to xen 3-testing I have the problem
that domain0 consumes more and more memory on domU networktraffic.
It is about 50 bytes per packet that gets lost.
I reproduced the bug on another machine.
In normal bridged setup all works fine.
I changed the setup in the following way:
- added an ip address to the bridge (in another subnet (B))
- changed domU ip address to a net B address
- added masquerading for eth0 in the postrouting-chain in dom0
After that I pinged a host outside this machine.
Sending and receiving 100.000 pakets results to a
dom0-memory-consumption increasement of about 5 MB!
I have to restart this machine once a day for not running out of memory.
What can I do?
Patrick
^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: xen 3 dom0 eats memory
@ 2006-01-04 14:34 Ian Pratt
2006-01-04 16:22 ` Patrick Scharrenberg
0 siblings, 1 reply; 12+ messages in thread
From: Ian Pratt @ 2006-01-04 14:34 UTC (permalink / raw)
To: Patrick Scharrenberg, Xen-devel
> Sending and receiving 100.000 pakets results to a
> dom0-memory-consumption increasement of about 5 MB!
When you've shipped a few million packets through the machine please
post the output of /proc/slabinfo
Ian
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: xen 3 dom0 eats memory
2006-01-04 13:43 Patrick Scharrenberg
@ 2006-01-04 14:35 ` Keir Fraser
2006-01-04 14:47 ` Patrick Scharrenberg
0 siblings, 1 reply; 12+ messages in thread
From: Keir Fraser @ 2006-01-04 14:35 UTC (permalink / raw)
To: Patrick Scharrenberg; +Cc: Xen-devel
> I changed the setup in the following way:
> - added an ip address to the bridge (in another subnet (B))
> - changed domU ip address to a net B address
> - added masquerading for eth0 in the postrouting-chain in dom0
What iptables rules do you use to set this up? Is the gateway address
for domU the net B address interface you add to the bridge?
It's worth trying 'ethtool -K eth0 tx off' in domU to turn off checksum
offload, just in case that is causing problems.
-- Keir
> After that I pinged a host outside this machine.
>
> Sending and receiving 100.000 pakets results to a
> dom0-memory-consumption increasement of about 5 MB!
>
> I have to restart this machine once a day for not running out of
> memory.
>
> What can I do?
>
> Patrick
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: xen 3 dom0 eats memory
2006-01-04 14:35 ` Keir Fraser
@ 2006-01-04 14:47 ` Patrick Scharrenberg
2006-01-04 14:58 ` Keir Fraser
0 siblings, 1 reply; 12+ messages in thread
From: Patrick Scharrenberg @ 2006-01-04 14:47 UTC (permalink / raw)
To: Keir Fraser; +Cc: Xen-devel
>> I changed the setup in the following way:
>> - added an ip address to the bridge (in another subnet (B))
>> - changed domU ip address to a net B address
>> - added masquerading for eth0 in the postrouting-chain in dom0
>
> What iptables rules do you use to set this up?
I used "iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE" for
masquerading.
> Is the gateway address for domU the net B address interface you add to
> the bridge?
Yes that right, i forgot to mention that.
I have one official address on dom0 eth0 and a privat class B network
for the domU's.
The address used on the bridge is from this private network and the
gateway for the domU's
> It's worth trying 'ethtool -K eth0 tx off' in domU to turn off
> checksum offload, just in case that is causing problems.
Checksum offload is turned off in all domU's.
The problem only appears if the pakets are masqueraded. Pinging the
gateway-address (the one on the bridge-if) or the dom0-eth0-address
causes no memory consumption
Patrick
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: xen 3 dom0 eats memory
2006-01-04 14:47 ` Patrick Scharrenberg
@ 2006-01-04 14:58 ` Keir Fraser
2006-01-04 15:35 ` Patrick Scharrenberg
0 siblings, 1 reply; 12+ messages in thread
From: Keir Fraser @ 2006-01-04 14:58 UTC (permalink / raw)
To: Patrick Scharrenberg; +Cc: Xen-devel
On 4 Jan 2006, at 14:47, Patrick Scharrenberg wrote:
>> What iptables rules do you use to set this up?
> I used "iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE" for
> masquerading.
>
>> Is the gateway address for domU the net B address interface you add
>> to the bridge?
> Yes that right, i forgot to mention that.
>
> I have one official address on dom0 eth0 and a privat class B network
> for the domU's.
> The address used on the bridge is from this private network and the
> gateway for the domU's
What interface do you attach the domU gateway address to?
-- Keir
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: xen 3 dom0 eats memory
2006-01-04 14:58 ` Keir Fraser
@ 2006-01-04 15:35 ` Patrick Scharrenberg
2006-01-04 15:52 ` Keir Fraser
0 siblings, 1 reply; 12+ messages in thread
From: Patrick Scharrenberg @ 2006-01-04 15:35 UTC (permalink / raw)
To: Keir Fraser; +Cc: Xen-devel
>>> Is the gateway address for domU the net B address interface you add
>>> to the bridge?
>> Yes that right, i forgot to mention that.
>>
>> I have one official address on dom0 eth0 and a privat class B network
>> for the domU's.
>> The address used on the bridge is from this private network and the
>> gateway for the domU's
>
> What interface do you attach the domU gateway address to?
>
it's the xen-bridge-interface where I set the domU gateway address.
Patrick
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: xen 3 dom0 eats memory
2006-01-04 15:35 ` Patrick Scharrenberg
@ 2006-01-04 15:52 ` Keir Fraser
2006-01-04 16:39 ` Patrick Scharrenberg
0 siblings, 1 reply; 12+ messages in thread
From: Keir Fraser @ 2006-01-04 15:52 UTC (permalink / raw)
To: Patrick Scharrenberg; +Cc: Xen-devel
On 4 Jan 2006, at 15:35, Patrick Scharrenberg wrote:
>>>> Is the gateway address for domU the net B address interface you add
>>>> to the bridge?
>>> Yes that right, i forgot to mention that.
>>>
>>> I have one official address on dom0 eth0 and a privat class B network
>>> for the domU's.
>>> The address used on the bridge is from this private network and the
>>> gateway for the domU's
>>
>> What interface do you attach the domU gateway address to?
>>
> it's the xen-bridge-interface where I set the domU gateway address.
I can't repro the problem. My setup is that the domU vif is the only
interface I attach to the bridge (eth0 is not attached). I give the
bridge address 10.0.0.1, enable IP forwarding, and set up IP masquerade
on eth0. I set domU IP address to 10.0.02 gw 10.0.0.1 and disable
transmit checksumming. I then did a TCP bulk transfer to an external
host (a few million packets) and observed no memory leak in domain 0.
-- Keir
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: xen 3 dom0 eats memory
2006-01-04 14:34 xen 3 dom0 eats memory Ian Pratt
@ 2006-01-04 16:22 ` Patrick Scharrenberg
2006-01-04 16:43 ` Keir Fraser
0 siblings, 1 reply; 12+ messages in thread
From: Patrick Scharrenberg @ 2006-01-04 16:22 UTC (permalink / raw)
To: Ian Pratt; +Cc: Xen-devel
[-- Attachment #1: Type: text/plain, Size: 2600 bytes --]
>> Sending and receiving 100.000 pakets results to a
>> dom0-memory-consumption increasement of about 5 MB!
>>
>
> When you've shipped a few million packets through the machine please
> post the output of /proc/slabinfo
>
Okay, I shipped arround 3million packets and here are the results (see
attached files).
slabinfo_a is the output before the tests and slabinfo_b is after the tests.
Here the output of free before..
total used free shared buffers cached
Mem: 700416 61288 639128 0 2984 19268
-/+ buffers/cache: 39036 661380
Swap: 0 0 0
and after the test:
total used free shared buffers cached
Mem: 700416 258388 442028 0 2996 19392
-/+ buffers/cache: 236000 464416
Swap: 0 0 0
I used floodping to generate the packets and found that the interface
stats for peth0 in dom0 are not correct either.
domU eth0 shows:
eth0 Link encap:Ethernet HWaddr 00:16:3E:05:B2:64
inet addr:192.168.37.2 Bcast:192.168.37.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3000075 errors:0 dropped:0 overruns:0 frame:0
TX packets:3000028 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:294006770 (280.3 MiB) TX bytes:294001488 (280.3 MiB)
rx bytes and tx bytes is nearly the same.
But in dom0:
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:3000123 errors:0 dropped:0 overruns:0 frame:0
TX packets:3000078 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:294010467 (280.3 MiB) TX bytes:306006234 (291.8 MiB)
Interrupt:17 Memory:e8000000-0
rx bytes and tx bytes differ in about 11 MB!
In dom0 nothing else ran, and on the (crossovered) pinged host, rx and
tx are also the same:
eth1 Link encap:Ethernet HWaddr 00:0E:0C:22:0E:55
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4700954 errors:0 dropped:0 overruns:0 frame:0
TX packets:4701065 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:479480546 (457.2 MiB) TX bytes:479508173 (457.2 MiB)
Base address:0x9400 Memory:e6000000-e6020000
(the higher values result from a second test)
I hope this helps!?
Patrick
[-- Attachment #2: slabinfo_a --]
[-- Type: text/plain, Size: 13918 bytes --]
total used free shared buffers cached
Mem: 700416 61288 639128 0 2984 19268
-/+ buffers/cache: 39036 661380
Swap: 0 0 0
slabinfo - version: 2.1
# name <active_objs> <num_objs> <objsize> <objperslab> <pagesperslab> : tunables <limit> <batchcount> <sharedfactor> : slabdata <active_slabs> <num_slabs> <sharedavail>
rpc_buffers 8 8 2048 2 1 : tunables 24 12 0 : slabdata 4 4 0
rpc_tasks 8 20 192 20 1 : tunables 120 60 0 : slabdata 1 1 0
rpc_inode_cache 0 0 416 9 1 : tunables 54 27 0 : slabdata 0 0 0
bridge_fdb_cache 6 61 64 61 1 : tunables 120 60 0 : slabdata 1 1 0
UNIX 87 88 352 11 1 : tunables 54 27 0 : slabdata 8 8 0
tcp_tw_bucket 0 0 96 41 1 : tunables 120 60 0 : slabdata 0 0 0
tcp_bind_bucket 4 226 16 226 1 : tunables 120 60 0 : slabdata 1 1 0
tcp_open_request 0 0 64 61 1 : tunables 120 60 0 : slabdata 0 0 0
inet_peer_cache 2 61 64 61 1 : tunables 120 60 0 : slabdata 1 1 0
ip_fib_alias 13 226 16 226 1 : tunables 120 60 0 : slabdata 1 1 0
ip_fib_hash 13 119 32 119 1 : tunables 120 60 0 : slabdata 1 1 0
ip_dst_cache 8 15 256 15 1 : tunables 120 60 0 : slabdata 1 1 0
arp_cache 4 31 128 31 1 : tunables 120 60 0 : slabdata 1 1 0
RAW 2 9 448 9 1 : tunables 54 27 0 : slabdata 1 1 0
UDP 0 0 448 9 1 : tunables 54 27 0 : slabdata 0 0 0
TCP 4 4 960 4 1 : tunables 54 27 0 : slabdata 1 1 0
flow_cache 0 0 96 41 1 : tunables 120 60 0 : slabdata 0 0 0
dm-snapshot-in 128 162 48 81 1 : tunables 120 60 0 : slabdata 2 2 0
dm-snapshot-ex 0 0 16 226 1 : tunables 120 60 0 : slabdata 0 0 0
dm_tio 516 678 16 226 1 : tunables 120 60 0 : slabdata 3 3 0
dm_io 516 678 16 226 1 : tunables 120 60 0 : slabdata 3 3 0
uhci_urb_priv 0 0 44 88 1 : tunables 120 60 0 : slabdata 0 0 0
scsi_cmd_cache 11 11 352 11 1 : tunables 54 27 0 : slabdata 1 1 0
blkif_cache 1 31 128 31 1 : tunables 120 60 0 : slabdata 1 1 0
cfq_ioc_pool 0 0 24 156 1 : tunables 120 60 0 : slabdata 0 0 0
cfq_pool 0 0 104 38 1 : tunables 120 60 0 : slabdata 0 0 0
crq_pool 0 0 52 75 1 : tunables 120 60 0 : slabdata 0 0 0
deadline_drq 0 0 48 81 1 : tunables 120 60 0 : slabdata 0 0 0
as_arq 22 65 60 65 1 : tunables 120 60 0 : slabdata 1 1 0
nfs_write_data 36 36 448 9 1 : tunables 54 27 0 : slabdata 4 4 0
nfs_read_data 32 36 448 9 1 : tunables 54 27 0 : slabdata 4 4 0
nfs_inode_cache 0 0 544 7 1 : tunables 54 27 0 : slabdata 0 0 0
nfs_page 0 0 64 61 1 : tunables 120 60 0 : slabdata 0 0 0
isofs_inode_cache 0 0 320 12 1 : tunables 54 27 0 : slabdata 0 0 0
ext2_inode_cache 6423 6430 400 10 1 : tunables 54 27 0 : slabdata 643 643 0
journal_handle 0 0 20 185 1 : tunables 120 60 0 : slabdata 0 0 0
journal_head 0 0 52 75 1 : tunables 120 60 0 : slabdata 0 0 0
revoke_table 0 0 12 290 1 : tunables 120 60 0 : slabdata 0 0 0
revoke_record 0 0 16 226 1 : tunables 120 60 0 : slabdata 0 0 0
ext3_inode_cache 0 0 432 9 1 : tunables 54 27 0 : slabdata 0 0 0
ext3_xattr 0 0 44 88 1 : tunables 120 60 0 : slabdata 0 0 0
reiser_inode_cache 0 0 368 11 1 : tunables 54 27 0 : slabdata 0 0 0
dnotify_cache 0 0 20 185 1 : tunables 120 60 0 : slabdata 0 0 0
eventpoll_pwq 0 0 36 107 1 : tunables 120 60 0 : slabdata 0 0 0
eventpoll_epi 0 0 96 41 1 : tunables 120 60 0 : slabdata 0 0 0
kioctx 0 0 160 25 1 : tunables 120 60 0 : slabdata 0 0 0
kiocb 0 0 128 31 1 : tunables 120 60 0 : slabdata 0 0 0
fasync_cache 0 0 16 226 1 : tunables 120 60 0 : slabdata 0 0 0
shmem_inode_cache 5 10 384 10 1 : tunables 54 27 0 : slabdata 1 1 0
posix_timers_cache 0 0 96 41 1 : tunables 120 60 0 : slabdata 0 0 0
uid_cache 1 61 64 61 1 : tunables 120 60 0 : slabdata 1 1 0
sgpool-128 32 33 2560 3 2 : tunables 24 12 0 : slabdata 11 11 0
sgpool-64 32 33 1280 3 1 : tunables 24 12 0 : slabdata 11 11 0
sgpool-32 32 36 640 6 1 : tunables 54 27 0 : slabdata 6 6 0
sgpool-16 32 36 320 12 1 : tunables 54 27 0 : slabdata 3 3 0
sgpool-8 34 50 160 25 1 : tunables 120 60 0 : slabdata 2 2 0
blkdev_ioc 16 156 24 156 1 : tunables 120 60 0 : slabdata 1 1 0
blkdev_queue 31 40 376 10 1 : tunables 54 27 0 : slabdata 4 4 0
blkdev_requests 24 54 148 27 1 : tunables 120 60 0 : slabdata 2 2 0
biovec-(256) 260 260 3072 2 2 : tunables 24 12 0 : slabdata 130 130 0
biovec-128 264 265 1536 5 2 : tunables 24 12 0 : slabdata 53 53 0
biovec-64 272 275 768 5 1 : tunables 54 27 0 : slabdata 55 55 0
biovec-16 272 280 192 20 1 : tunables 120 60 0 : slabdata 14 14 0
biovec-4 305 305 64 61 1 : tunables 120 60 0 : slabdata 5 5 0
biovec-1 292 452 16 226 1 : tunables 120 60 0 : slabdata 2 2 0
bio 321 369 96 41 1 : tunables 120 60 0 : slabdata 9 9 0
file_lock_cache 4 45 88 45 1 : tunables 120 60 0 : slabdata 1 1 0
xen-skb-65536 0 0 65536 1 16 : tunables 8 4 0 : slabdata 0 0 0
xen-skb-32768 0 0 32768 1 8 : tunables 8 4 0 : slabdata 0 0 0
xen-skb-16384 0 0 16384 1 4 : tunables 8 4 0 : slabdata 0 0 0
xen-skb-8192 0 0 8192 1 2 : tunables 8 4 0 : slabdata 0 0 0
xen-skb-4096 0 0 4096 1 1 : tunables 24 12 0 : slabdata 0 0 0
xen-skb-2048 384 386 2048 2 1 : tunables 24 12 0 : slabdata 193 193 0
xen-skb-512 0 0 512 8 1 : tunables 54 27 0 : slabdata 0 0 0
sock_inode_cache 110 110 352 11 1 : tunables 54 27 0 : slabdata 10 10 0
skbuff_head_cache 386 400 192 20 1 : tunables 120 60 0 : slabdata 20 20 0
proc_inode_cache 254 273 308 13 1 : tunables 54 27 0 : slabdata 21 21 0
sigqueue 0 27 148 27 1 : tunables 120 60 0 : slabdata 0 1 0
radix_tree_node 1105 1106 276 14 1 : tunables 54 27 0 : slabdata 79 79 0
bdev_cache 6 9 416 9 1 : tunables 54 27 0 : slabdata 1 1 0
sysfs_dir_cache 3361 3424 36 107 1 : tunables 120 60 0 : slabdata 32 32 0
mnt_cache 16 41 96 41 1 : tunables 120 60 0 : slabdata 1 1 0
inode_cache 1150 1157 292 13 1 : tunables 54 27 0 : slabdata 89 89 0
dentry_cache 9668 9715 136 29 1 : tunables 120 60 0 : slabdata 335 335 0
filp 355 475 160 25 1 : tunables 120 60 0 : slabdata 19 19 0
names_cache 1 1 4096 1 1 : tunables 24 12 0 : slabdata 1 1 0
idr_layer_cache 110 116 136 29 1 : tunables 120 60 0 : slabdata 4 4 0
buffer_head 3880 3969 48 81 1 : tunables 120 60 0 : slabdata 49 49 0
mm_struct 39 77 576 7 1 : tunables 54 27 0 : slabdata 11 11 0
vm_area_struct 626 855 88 45 1 : tunables 120 60 0 : slabdata 19 19 0
fs_cache 38 119 32 119 1 : tunables 120 60 0 : slabdata 1 1 0
files_cache 39 63 416 9 1 : tunables 54 27 0 : slabdata 7 7 0
signal_cache 67 88 352 11 1 : tunables 54 27 0 : slabdata 8 8 0
sighand_cache 45 45 1312 3 1 : tunables 24 12 0 : slabdata 15 15 0
task_struct 54 54 1264 3 1 : tunables 24 12 0 : slabdata 18 18 0
anon_vma 321 814 8 407 1 : tunables 120 60 0 : slabdata 2 2 0
pgd 25 25 4096 1 1 : tunables 24 12 0 : slabdata 25 25 0
size-131072(DMA) 0 0 131072 1 32 : tunables 8 4 0 : slabdata 0 0 0
size-131072 0 0 131072 1 32 : tunables 8 4 0 : slabdata 0 0 0
size-65536(DMA) 0 0 65536 1 16 : tunables 8 4 0 : slabdata 0 0 0
size-65536 2 2 65536 1 16 : tunables 8 4 0 : slabdata 2 2 0
size-32768(DMA) 0 0 32768 1 8 : tunables 8 4 0 : slabdata 0 0 0
size-32768 0 0 32768 1 8 : tunables 8 4 0 : slabdata 0 0 0
size-16384(DMA) 0 0 16384 1 4 : tunables 8 4 0 : slabdata 0 0 0
size-16384 0 0 16384 1 4 : tunables 8 4 0 : slabdata 0 0 0
size-8192(DMA) 0 0 8192 1 2 : tunables 8 4 0 : slabdata 0 0 0
size-8192 56 56 8192 1 2 : tunables 8 4 0 : slabdata 56 56 0
size-4096(DMA) 0 0 4096 1 1 : tunables 24 12 0 : slabdata 0 0 0
size-4096 22 22 4096 1 1 : tunables 24 12 0 : slabdata 22 22 0
size-2048(DMA) 0 0 2048 2 1 : tunables 24 12 0 : slabdata 0 0 0
size-2048 18 18 2048 2 1 : tunables 24 12 0 : slabdata 9 9 0
size-1024(DMA) 0 0 1024 4 1 : tunables 54 27 0 : slabdata 0 0 0
size-1024 178 192 1024 4 1 : tunables 54 27 0 : slabdata 48 48 0
size-512(DMA) 0 0 512 8 1 : tunables 54 27 0 : slabdata 0 0 0
size-512 165 168 512 8 1 : tunables 54 27 0 : slabdata 21 21 0
size-256(DMA) 0 0 256 15 1 : tunables 120 60 0 : slabdata 0 0 0
size-256 120 120 256 15 1 : tunables 120 60 0 : slabdata 8 8 0
size-192(DMA) 0 0 192 20 1 : tunables 120 60 0 : slabdata 0 0 0
size-192 60 60 192 20 1 : tunables 120 60 0 : slabdata 3 3 0
size-128(DMA) 0 0 128 31 1 : tunables 120 60 0 : slabdata 0 0 0
size-128 1812 1829 128 31 1 : tunables 120 60 0 : slabdata 59 59 0
size-64(DMA) 0 0 64 61 1 : tunables 120 60 0 : slabdata 0 0 0
size-64 1708 1708 64 61 1 : tunables 120 60 0 : slabdata 28 28 0
size-32(DMA) 0 0 32 119 1 : tunables 120 60 0 : slabdata 0 0 0
size-32 2261 2261 32 119 1 : tunables 120 60 0 : slabdata 19 19 0
kmem_cache 155 155 128 31 1 : tunables 120 60 0 : slabdata 5 5 0
[-- Attachment #3: slabinfo_b --]
[-- Type: text/plain, Size: 14983 bytes --]
total used free shared buffers cached
Mem: 700416 258388 442028 0 2996 19392
-/+ buffers/cache: 236000 464416
Swap: 0 0 0
slabinfo - version: 2.1
# name <active_objs> <num_objs> <objsize> <objperslab> <pagesperslab> : tunables <limit> <batchcount> <sharedfactor> : slabdata <active_slabs> <num_slabs> <sharedavail>
ip_conntrack_expect 0 0 84 47 1 : tunables 120 60 0 : slabdata 0 0 0
ip_conntrack 0 0 244 16 1 : tunables 120 60 0 : slabdata 0 0 0
rpc_buffers 8 8 2048 2 1 : tunables 24 12 0 : slabdata 4 4 0
rpc_tasks 8 20 192 20 1 : tunables 120 60 0 : slabdata 1 1 0
rpc_inode_cache 0 0 416 9 1 : tunables 54 27 0 : slabdata 0 0 0
bridge_fdb_cache 5 61 64 61 1 : tunables 120 60 0 : slabdata 1 1 0
UNIX 87 88 352 11 1 : tunables 54 27 0 : slabdata 8 8 0
tcp_tw_bucket 0 0 96 41 1 : tunables 120 60 0 : slabdata 0 0 0
tcp_bind_bucket 4 226 16 226 1 : tunables 120 60 0 : slabdata 1 1 0
tcp_open_request 0 0 64 61 1 : tunables 120 60 0 : slabdata 0 0 0
inet_peer_cache 1 61 64 61 1 : tunables 120 60 0 : slabdata 1 1 0
ip_fib_alias 13 226 16 226 1 : tunables 120 60 0 : slabdata 1 1 0
ip_fib_hash 13 119 32 119 1 : tunables 120 60 0 : slabdata 1 1 0
ip_dst_cache 7 15 256 15 1 : tunables 120 60 0 : slabdata 1 1 0
arp_cache 3 31 128 31 1 : tunables 120 60 0 : slabdata 1 1 0
RAW 2 9 448 9 1 : tunables 54 27 0 : slabdata 1 1 0
UDP 0 0 448 9 1 : tunables 54 27 0 : slabdata 0 0 0
TCP 4 4 960 4 1 : tunables 54 27 0 : slabdata 1 1 0
flow_cache 0 0 96 41 1 : tunables 120 60 0 : slabdata 0 0 0
dm-snapshot-in 128 162 48 81 1 : tunables 120 60 0 : slabdata 2 2 0
dm-snapshot-ex 0 0 16 226 1 : tunables 120 60 0 : slabdata 0 0 0
dm_tio 512 678 16 226 1 : tunables 120 60 0 : slabdata 3 3 0
dm_io 512 678 16 226 1 : tunables 120 60 0 : slabdata 3 3 0
uhci_urb_priv 0 0 44 88 1 : tunables 120 60 0 : slabdata 0 0 0
scsi_cmd_cache 2 11 352 11 1 : tunables 54 27 0 : slabdata 1 1 0
blkif_cache 1 31 128 31 1 : tunables 120 60 0 : slabdata 1 1 0
cfq_ioc_pool 0 0 24 156 1 : tunables 120 60 0 : slabdata 0 0 0
cfq_pool 0 0 104 38 1 : tunables 120 60 0 : slabdata 0 0 0
crq_pool 0 0 52 75 1 : tunables 120 60 0 : slabdata 0 0 0
deadline_drq 0 0 48 81 1 : tunables 120 60 0 : slabdata 0 0 0
as_arq 16 65 60 65 1 : tunables 120 60 0 : slabdata 1 1 0
nfs_write_data 36 36 448 9 1 : tunables 54 27 0 : slabdata 4 4 0
nfs_read_data 32 36 448 9 1 : tunables 54 27 0 : slabdata 4 4 0
nfs_inode_cache 0 0 544 7 1 : tunables 54 27 0 : slabdata 0 0 0
nfs_page 0 0 64 61 1 : tunables 120 60 0 : slabdata 0 0 0
isofs_inode_cache 0 0 320 12 1 : tunables 54 27 0 : slabdata 0 0 0
ext2_inode_cache 6427 6430 400 10 1 : tunables 54 27 0 : slabdata 643 643 0
journal_handle 0 0 20 185 1 : tunables 120 60 0 : slabdata 0 0 0
journal_head 0 0 52 75 1 : tunables 120 60 0 : slabdata 0 0 0
revoke_table 0 0 12 290 1 : tunables 120 60 0 : slabdata 0 0 0
revoke_record 0 0 16 226 1 : tunables 120 60 0 : slabdata 0 0 0
ext3_inode_cache 0 0 432 9 1 : tunables 54 27 0 : slabdata 0 0 0
ext3_xattr 0 0 44 88 1 : tunables 120 60 0 : slabdata 0 0 0
reiser_inode_cache 0 0 368 11 1 : tunables 54 27 0 : slabdata 0 0 0
dnotify_cache 0 0 20 185 1 : tunables 120 60 0 : slabdata 0 0 0
eventpoll_pwq 0 0 36 107 1 : tunables 120 60 0 : slabdata 0 0 0
eventpoll_epi 0 0 96 41 1 : tunables 120 60 0 : slabdata 0 0 0
kioctx 0 0 160 25 1 : tunables 120 60 0 : slabdata 0 0 0
kiocb 0 0 128 31 1 : tunables 120 60 0 : slabdata 0 0 0
fasync_cache 0 0 16 226 1 : tunables 120 60 0 : slabdata 0 0 0
shmem_inode_cache 5 10 384 10 1 : tunables 54 27 0 : slabdata 1 1 0
posix_timers_cache 0 0 96 41 1 : tunables 120 60 0 : slabdata 0 0 0
uid_cache 1 61 64 61 1 : tunables 120 60 0 : slabdata 1 1 0
sgpool-128 32 33 2560 3 2 : tunables 24 12 0 : slabdata 11 11 0
sgpool-64 32 33 1280 3 1 : tunables 24 12 0 : slabdata 11 11 0
sgpool-32 32 36 640 6 1 : tunables 54 27 0 : slabdata 6 6 0
sgpool-16 32 36 320 12 1 : tunables 54 27 0 : slabdata 3 3 0
sgpool-8 32 50 160 25 1 : tunables 120 60 0 : slabdata 2 2 0
blkdev_ioc 16 156 24 156 1 : tunables 120 60 0 : slabdata 1 1 0
blkdev_queue 31 40 376 10 1 : tunables 54 27 0 : slabdata 4 4 0
blkdev_requests 18 27 148 27 1 : tunables 120 60 0 : slabdata 1 1 0
biovec-(256) 260 260 3072 2 2 : tunables 24 12 0 : slabdata 130 130 0
biovec-128 264 265 1536 5 2 : tunables 24 12 0 : slabdata 53 53 0
biovec-64 272 275 768 5 1 : tunables 54 27 0 : slabdata 55 55 0
biovec-16 272 280 192 20 1 : tunables 120 60 0 : slabdata 14 14 0
biovec-4 272 305 64 61 1 : tunables 120 60 0 : slabdata 5 5 0
biovec-1 272 452 16 226 1 : tunables 120 60 0 : slabdata 2 2 0
bio 272 287 96 41 1 : tunables 120 60 0 : slabdata 7 7 0
file_lock_cache 4 45 88 45 1 : tunables 120 60 0 : slabdata 1 1 0
xen-skb-65536 0 0 65536 1 16 : tunables 8 4 0 : slabdata 0 0 0
xen-skb-32768 0 0 32768 1 8 : tunables 8 4 0 : slabdata 0 0 0
xen-skb-16384 0 0 16384 1 4 : tunables 8 4 0 : slabdata 0 0 0
xen-skb-8192 0 0 8192 1 2 : tunables 8 4 0 : slabdata 0 0 0
xen-skb-4096 0 0 4096 1 1 : tunables 24 12 0 : slabdata 0 0 0
xen-skb-2048 384 386 2048 2 1 : tunables 24 12 0 : slabdata 193 193 0
xen-skb-512 0 0 512 8 1 : tunables 54 27 0 : slabdata 0 0 0
sock_inode_cache 110 110 352 11 1 : tunables 54 27 0 : slabdata 10 10 0
skbuff_head_cache 384 400 192 20 1 : tunables 120 60 0 : slabdata 20 20 0
proc_inode_cache 254 273 308 13 1 : tunables 54 27 0 : slabdata 21 21 0
sigqueue 0 0 148 27 1 : tunables 120 60 0 : slabdata 0 0 0
radix_tree_node 1113 1120 276 14 1 : tunables 54 27 0 : slabdata 80 80 0
bdev_cache 6 9 416 9 1 : tunables 54 27 0 : slabdata 1 1 0
sysfs_dir_cache 3416 3424 36 107 1 : tunables 120 60 0 : slabdata 32 32 0
mnt_cache 16 41 96 41 1 : tunables 120 60 0 : slabdata 1 1 0
inode_cache 1157 1157 292 13 1 : tunables 54 27 0 : slabdata 89 89 0
dentry_cache 9643 9715 136 29 1 : tunables 120 60 0 : slabdata 335 335 0
filp 405 475 160 25 1 : tunables 120 60 0 : slabdata 19 19 0
names_cache 1 1 4096 1 1 : tunables 24 12 0 : slabdata 1 1 0
idr_layer_cache 110 116 136 29 1 : tunables 120 60 0 : slabdata 4 4 0
buffer_head 3961 3969 48 81 1 : tunables 120 60 0 : slabdata 49 49 0
mm_struct 26 77 576 7 1 : tunables 54 27 0 : slabdata 11 11 0
vm_area_struct 634 855 88 45 1 : tunables 120 60 0 : slabdata 19 19 0
fs_cache 38 119 32 119 1 : tunables 120 60 0 : slabdata 1 1 0
files_cache 39 63 416 9 1 : tunables 54 27 0 : slabdata 7 7 0
signal_cache 67 88 352 11 1 : tunables 54 27 0 : slabdata 8 8 0
sighand_cache 45 45 1312 3 1 : tunables 24 12 0 : slabdata 15 15 0
task_struct 54 54 1264 3 1 : tunables 24 12 0 : slabdata 18 18 0
anon_vma 314 814 8 407 1 : tunables 120 60 0 : slabdata 2 2 0
pgd 25 25 4096 1 1 : tunables 24 12 0 : slabdata 25 25 0
size-131072(DMA) 0 0 131072 1 32 : tunables 8 4 0 : slabdata 0 0 0
size-131072 0 0 131072 1 32 : tunables 8 4 0 : slabdata 0 0 0
size-65536(DMA) 0 0 65536 1 16 : tunables 8 4 0 : slabdata 0 0 0
size-65536 2 2 65536 1 16 : tunables 8 4 0 : slabdata 2 2 0
size-32768(DMA) 0 0 32768 1 8 : tunables 8 4 0 : slabdata 0 0 0
size-32768 0 0 32768 1 8 : tunables 8 4 0 : slabdata 0 0 0
size-16384(DMA) 0 0 16384 1 4 : tunables 8 4 0 : slabdata 0 0 0
size-16384 0 0 16384 1 4 : tunables 8 4 0 : slabdata 0 0 0
size-8192(DMA) 0 0 8192 1 2 : tunables 8 4 0 : slabdata 0 0 0
size-8192 56 56 8192 1 2 : tunables 8 4 0 : slabdata 56 56 0
size-4096(DMA) 0 0 4096 1 1 : tunables 24 12 0 : slabdata 0 0 0
size-4096 22 22 4096 1 1 : tunables 24 12 0 : slabdata 22 22 0
size-2048(DMA) 0 0 2048 2 1 : tunables 24 12 0 : slabdata 0 0 0
size-2048 19 20 2048 2 1 : tunables 24 12 0 : slabdata 10 10 0
size-1024(DMA) 0 0 1024 4 1 : tunables 54 27 0 : slabdata 0 0 0
size-1024 165 192 1024 4 1 : tunables 54 27 0 : slabdata 48 48 0
size-512(DMA) 0 0 512 8 1 : tunables 54 27 0 : slabdata 0 0 0
size-512 167 168 512 8 1 : tunables 54 27 0 : slabdata 21 21 0
size-256(DMA) 0 0 256 15 1 : tunables 120 60 0 : slabdata 0 0 0
size-256 120 120 256 15 1 : tunables 120 60 0 : slabdata 8 8 0
size-192(DMA) 0 0 192 20 1 : tunables 120 60 0 : slabdata 0 0 0
size-192 60 60 192 20 1 : tunables 120 60 0 : slabdata 3 3 0
size-128(DMA) 0 0 128 31 1 : tunables 120 60 0 : slabdata 0 0 0
size-128 1837 1860 128 31 1 : tunables 120 60 0 : slabdata 60 60 0
size-64(DMA) 0 0 64 61 1 : tunables 120 60 0 : slabdata 0 0 0
size-64 3001718 3001749 64 61 1 : tunables 120 60 0 : slabdata 49209 49209 0
size-32(DMA) 0 0 32 119 1 : tunables 120 60 0 : slabdata 0 0 0
size-32 2321 2380 32 119 1 : tunables 120 60 0 : slabdata 20 20 0
kmem_cache 155 155 128 31 1 : tunables 120 60 0 : slabdata 5 5 0
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:3000123 errors:0 dropped:0 overruns:0 frame:0
TX packets:3000078 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:294010467 (280.3 MiB) TX bytes:306006234 (291.8 MiB)
Interrupt:17 Memory:e8000000-0
eth0 Link encap:Ethernet HWaddr 00:0E:A6:3D:B0:F0
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:123 errors:0 dropped:0 overruns:0 frame:0
TX packets:3000075 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10358 (10.1 KiB) TX bytes:294004914 (280.3 MiB)
[-- Attachment #4: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: xen 3 dom0 eats memory
2006-01-04 15:52 ` Keir Fraser
@ 2006-01-04 16:39 ` Patrick Scharrenberg
2006-01-04 16:52 ` Keir Fraser
0 siblings, 1 reply; 12+ messages in thread
From: Patrick Scharrenberg @ 2006-01-04 16:39 UTC (permalink / raw)
To: Keir Fraser; +Cc: Xen-devel
Keir Fraser schrieb:
>
> On 4 Jan 2006, at 15:35, Patrick Scharrenberg wrote:
>
>>>>> Is the gateway address for domU the net B address interface you add
>>>>> to the bridge?
>>>> Yes that right, i forgot to mention that.
>>>>
>>>> I have one official address on dom0 eth0 and a privat class B network
>>>> for the domU's.
>>>> The address used on the bridge is from this private network and the
>>>> gateway for the domU's
>>>
>>> What interface do you attach the domU gateway address to?
>>>
>> it's the xen-bridge-interface where I set the domU gateway address.
>
> I can't repro the problem. My setup is that the domU vif is the only
> interface I attach to the bridge (eth0 is not attached). I give the
> bridge address 10.0.0.1, enable IP forwarding, and set up IP
> masquerade on eth0. I set domU IP address to 10.0.02 gw 10.0.0.1 and
> disable transmit checksumming. I then did a TCP bulk transfer to an
> external host (a few million packets) and observed no memory leak in
> domain 0.
>
Hmm.. thats strange, since I did nothing special.
Here once more what I did, maybe (hopefully) we misunderstood:
eth0 has my internet ip address.
I used the network-bridge-script to setup the (xen-) networking,
set up ip 192.168.37.254 on xenbr0.
Then I startet domU.
After that I added masquerading to eth0.
I have the following interfaces in the bridge: peth0, vif0.0, vif1.0
I'm using debian sarge as os. Maybe they set something special in their
networking-scripts?
It is a test-machine, so i can give you the root-pw, if nothing helps.
Patrick
> -- Keir
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: xen 3 dom0 eats memory
2006-01-04 16:22 ` Patrick Scharrenberg
@ 2006-01-04 16:43 ` Keir Fraser
0 siblings, 0 replies; 12+ messages in thread
From: Keir Fraser @ 2006-01-04 16:43 UTC (permalink / raw)
To: Patrick Scharrenberg; +Cc: Ian Pratt, Xen-devel
On 4 Jan 2006, at 16:22, Patrick Scharrenberg wrote:
>
> I used floodping to generate the packets and found that the interface
> stats for peth0 in dom0 are not correct either.
If all your domU interfaces will be NATed then there's no need to be
using Ethernet bridging at all. You probably don't want to use the
/etc/xen/scripts/network-bridge and vif-bridge scripts, replacing them
with your own which would place a domU-specific virtual gateway address
on each vifx.0 in dom0. Then enable IP forwarding and IP masquerade on
eth0 and you should be away, with no Ethernet bridging required.
-- Keir
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: xen 3 dom0 eats memory
2006-01-04 16:39 ` Patrick Scharrenberg
@ 2006-01-04 16:52 ` Keir Fraser
2006-01-06 11:17 ` Patrick Scharrenberg
0 siblings, 1 reply; 12+ messages in thread
From: Keir Fraser @ 2006-01-04 16:52 UTC (permalink / raw)
To: Patrick Scharrenberg; +Cc: Xen-devel
On 4 Jan 2006, at 16:39, Patrick Scharrenberg wrote:
> I used the network-bridge-script to setup the (xen-) networking,
> set up ip 192.168.37.254 on xenbr0.
> Then I startet domU.
> After that I added masquerading to eth0.
Possibly you can sidestep the whole issue, and end up with faster and
simpler networking setup in dom0, by not using network-bridge and
vif-bridge scripts at all. Instead make your own (much much simpler)
scripts to set up NAT.
-- Keir
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: xen 3 dom0 eats memory
2006-01-04 16:52 ` Keir Fraser
@ 2006-01-06 11:17 ` Patrick Scharrenberg
0 siblings, 0 replies; 12+ messages in thread
From: Patrick Scharrenberg @ 2006-01-06 11:17 UTC (permalink / raw)
To: Keir Fraser; +Cc: Xen-devel
Hey Keir!
>> I used the network-bridge-script to setup the (xen-) networking,
>> set up ip 192.168.37.254 on xenbr0.
>> Then I startet domU.
>> After that I added masquerading to eth0.
>
> Possibly you can sidestep the whole issue, and end up with faster and
> simpler networking setup in dom0, by not using network-bridge and
> vif-bridge scripts at all. Instead make your own (much much simpler)
> scripts to set up NAT.
I found another odd thing regarding the vif-interfaces that my has
something to do with the problem mentioned before:
I have a high rate of dropped tx packets on all vif's except for vif 0.0.
As mentioned before, the config without eth0->peth0 renaming and without
vif for dom0 and the rest of the vif's in the bridge works well.
Patrick
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2006-01-06 11:17 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-01-04 14:34 xen 3 dom0 eats memory Ian Pratt
2006-01-04 16:22 ` Patrick Scharrenberg
2006-01-04 16:43 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2006-01-04 13:43 Patrick Scharrenberg
2006-01-04 14:35 ` Keir Fraser
2006-01-04 14:47 ` Patrick Scharrenberg
2006-01-04 14:58 ` Keir Fraser
2006-01-04 15:35 ` Patrick Scharrenberg
2006-01-04 15:52 ` Keir Fraser
2006-01-04 16:39 ` Patrick Scharrenberg
2006-01-04 16:52 ` Keir Fraser
2006-01-06 11:17 ` Patrick Scharrenberg
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.