From: Thomas Graf <tgraf@redhat.com>
To: Ben Pfaff <blp@nicira.com>
Cc: jesse@nicira.com, dev@openvswitch.org, netdev@vger.kernel.org,
dborkman@redhat.com, ffusco@redhat.com, fleitner@redhat.com,
xiyou.wangcong@gmail.com
Subject: Re: [PATCH openvswitch v3] netlink: Implement & enable memory mapped netlink i/o
Date: Wed, 04 Dec 2013 18:20:53 +0100 [thread overview]
Message-ID: <529F6475.3090903@redhat.com> (raw)
In-Reply-To: <20131204163328.GE30874@nicira.com>
On 12/04/2013 05:33 PM, Ben Pfaff wrote:
> If I'm doing the calculations correctly, this mmaps 8 MB per ring-based
> Netlink socket on a system with 4 kB pages. OVS currently creates one
> Netlink socket for each datapath port. With 1000 ports (a moderate
> number; we sometimes test with more), that is 8 GB of address space. On
> a 32-bit architecture that is impossible. On a 64-bit architecture it
> is possible but it may reserve an actual 8 GB of RAM: OVS often runs
> with mlockall() since it is something of a soft real-time system (users
> don't want their packet delivery delayed to page data back in).
>
> Do you have any thoughts about this issue?
That's certainly a problem. I had the impression that the changes that
allow to consolidate multiple bridges to a single DP would minimize the
number of DPs used.
How about we limit the number of mmaped sockets to a configurable
maximum that defaults to 16 or 32?
next prev parent reply other threads:[~2013-12-04 17:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 11:19 [PATCH openvswitch v3] netlink: Implement & enable memory mapped netlink i/o Thomas Graf
[not found] ` <1d9af26b2798901c68ae9aef704d6313b71d3287.1386069453.git.tgraf-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-12-04 1:54 ` 答复: " Zhuangyuxin
[not found] ` <9C2DE4B8FE85984BA1B0581235F6B2ED0F5D440A-tJwL4pWccCZdGU6diIvhbAK1hpo4iccwjNknBlVQO8k@public.gmane.org>
2013-12-04 9:08 ` Thomas Graf
2013-12-04 16:33 ` Ben Pfaff
2013-12-04 17:20 ` Thomas Graf [this message]
[not found] ` <529F6475.3090903-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-12-04 17:56 ` Kais Belgaied
2013-12-04 18:08 ` Ben Pfaff
2013-12-04 21:48 ` Thomas Graf
2013-12-04 22:20 ` Jesse Gross
2013-12-05 22:08 ` Thomas Graf
2013-12-05 22:54 ` Ben Pfaff
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=529F6475.3090903@redhat.com \
--to=tgraf@redhat.com \
--cc=blp@nicira.com \
--cc=dborkman@redhat.com \
--cc=dev@openvswitch.org \
--cc=ffusco@redhat.com \
--cc=fleitner@redhat.com \
--cc=jesse@nicira.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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 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).