All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Diwaker Gupta <diwaker.lists@gmail.com>, xen-devel@lists.xensource.com
Subject: Re: n/w performance degradation
Date: Mon, 05 Dec 2005 18:26:19 -0800	[thread overview]
Message-ID: <4394F6CB.4080607@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D409B78@liverpoolst.ad.cl.cam.ac.uk>

Ian Pratt wrote:

>  > > What are your memory allocations? How much of a bump do you 
> 
>>get if you 
>>
>>>increase memory?
>>
>>Currently, both dom0 and the vm have 128MB. I rebooted with 
>>dom0 having 512MB and VM with 256 MB. Here are the numbers:
>>
>>dom0:
>>[  5]  0.0-10.0 sec    987 MBytes    828 Mbits/sec
>>
>>VM:
>>[  5]  0.0-10.0 sec    938 MBytes    787 Mbits/sec
>>
>>So getting slightly better. I haven't run these with SEDF 
>>though, above are using BVT.
> 
> 
> Ah, I expect I know what's going on here.
> 
> Linux sizes the default socket buffer size based on how much 'system'
> memory it has.
> 
> With a 128MB domU it probably defaults to just 64K. For 256MB it
> probably steps up to 128KB. You can prove this by setting
> /proc/sys/net/core/{r,w}mem_{max,default}.

For TCP sockets, you'll also have to bump up
net/ipv4/tcp_rmem[1,2] and net/ipv4/tcp_wmem[1,2],
don't forget.

Fow low mem systems, the default size of the tcp read buffer
(tcp_rmem[1]) is 43689, and max size (tcp_rmem[2]) is
2*43689, which is really too low to do network heavy
lifting.

> For a gigabit network you need at least 128KB.
> 
> Ian

At least.

thanks,
Nivedita

  parent reply	other threads:[~2005-12-06  2:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-06  1:42 n/w performance degradation Ian Pratt
2005-12-06  2:07 ` Diwaker Gupta
2005-12-06  2:26 ` Nivedita Singhvi [this message]
2005-12-06  8:02   ` Diwaker Gupta
  -- strict thread matches above, loose matches on Subject: below --
2005-12-06 10:42 Ian Pratt
2005-12-05 23:49 Ian Pratt
2005-12-06  0:06 ` Diwaker Gupta
2005-12-05 23:11 Diwaker Gupta
2005-12-05 23:23 ` Keir Fraser
2005-12-06  0:04   ` Diwaker Gupta
2005-12-06 11:20     ` Keir Fraser
2005-12-06  0:09 ` Nivedita Singhvi
2005-12-06  1:32   ` Diwaker Gupta
2005-12-06  2:15     ` Nivedita Singhvi

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=4394F6CB.4080607@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=diwaker.lists@gmail.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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.