From: Jason Wang <jasowang@redhat.com>
To: davem@davemloft.net, edumazet@google.com, hkchu@google.com,
mst@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Jason Wang <jasowang@redhat.com>
Subject: [net-next rfc 0/3] increase the limit of tuntap queues
Date: Wed, 19 Jun 2013 13:40:49 +0800 [thread overview]
Message-ID: <1371620452-49349-1-git-send-email-jasowang@redhat.com> (raw)
Hi all:
This series tries to increase the limit of tuntap queues. Histrocially there're
two reasons which prevent us from doing this:
- We store the hash buckets in tun_struct which results a very large size of
tun_struct, this high order memory allocation fail easily when the memory were
fragmented.
- The netdev_queue and netdev_rx_queue array in netdevice were allocated through
kmalloc, which may cause a high order memory allocation too when we have
several queues. E.g. sizeof(netdev_queue) is 320, which means a high order
allocation will happens when the device has more than 12 queues.
So this series tries to address those issues by switching to use flex array. All
entries were preallocated, and since flex array always do a order-0 allocation,
we can safely increase the limit after.
Only compile test, comments or review are more than welcomed.
Jason Wang (3):
net: avoid high order memory allocation for queues by using flex
array
tuntap: reduce the size of tun_struct by using flex array
tuntap: increase the max queues to 16
drivers/net/tun.c | 59 ++++++++++++++++++++++++++++++++------------
include/linux/netdevice.h | 13 ++++++----
net/core/dev.c | 57 +++++++++++++++++++++++++++++++------------
net/core/net-sysfs.c | 15 +++++++----
net/openvswitch/flow.c | 2 +-
5 files changed, 102 insertions(+), 44 deletions(-)
next reply other threads:[~2013-06-19 5:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 5:40 Jason Wang [this message]
2013-06-19 5:40 ` [net-next rfc 1/3] net: avoid high order memory allocation for queues by using flex array Jason Wang
2013-06-19 6:31 ` Eric Dumazet
2013-06-19 7:14 ` Jason Wang
2013-06-19 9:11 ` Michael S. Tsirkin
2013-06-19 9:56 ` Eric Dumazet
2013-06-19 12:22 ` Michael S. Tsirkin
2013-06-19 15:40 ` Michael S. Tsirkin
2013-06-19 15:58 ` Eric Dumazet
2013-06-19 16:06 ` David Laight
2013-06-19 16:06 ` David Laight
2013-06-19 16:28 ` Eric Dumazet
2013-06-19 18:07 ` Michael S. Tsirkin
2013-06-20 8:15 ` [PATCH net-next] net: allow large number of tx queues Eric Dumazet
2013-06-20 8:35 ` Michael S. Tsirkin
2013-06-21 6:41 ` Jason Wang
2013-06-21 7:12 ` Eric Dumazet
2013-06-23 10:29 ` Michael S. Tsirkin
2013-06-24 6:57 ` David Miller
2013-06-20 5:14 ` [net-next rfc 1/3] net: avoid high order memory allocation for queues by using flex array Jason Wang
2013-06-20 6:05 ` Eric Dumazet
2013-06-19 5:40 ` [net-next rfc 2/3] tuntap: reduce the size of tun_struct " Jason Wang
2013-06-19 5:40 ` [net-next rfc 3/3] tuntap: increase the max queues to 16 Jason Wang
2013-06-19 6:34 ` Eric Dumazet
2013-06-19 7:15 ` Jason Wang
2013-06-19 19:16 ` Jerry Chu
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=1371620452-49349-1-git-send-email-jasowang@redhat.com \
--to=jasowang@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkchu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.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 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.