From: Ravikiran G Thirumalai <kiran@in.ibm.com>
To: "David S. Miller " <davem@redhat.com>
Cc: netdev <netdev@oss.sgi.com>, linux-kernel@vger.kernel.org
Subject: [patch] Convert sockets_in_use to use per_cpu areas
Date: Mon, 23 Dec 2002 19:08:48 +0530 [thread overview]
Message-ID: <20021223190847.G23413@in.ibm.com> (raw)
Hi,
Here's a simple patch to change sockets_in_use to make use of
per-cpu areas.
I have couple of questions though...
1. Was this var made per-cpu just to avoid atomic_t or locking
or are there real life workloads which cause too many sock_alloc
and sock_releases to cause cacheline bouncing?
2. Is this var required? since we can just sum up all proto->stats.inuse
and remove this var altogether? (This var is read only for /proc
reporting)
Thanks,
Kiran
diff -ruN -X dontdiff linux-2.5.52/net/socket.c sockets_in_use-2.5.52/net/socket.c
--- linux-2.5.52/net/socket.c Mon Dec 16 07:37:53 2002
+++ sockets_in_use-2.5.52/net/socket.c Mon Dec 23 11:48:44 2002
@@ -189,10 +189,7 @@
* Statistics counters of the socket lists
*/
-static union {
- int counter;
- char __pad[SMP_CACHE_BYTES];
-} sockets_in_use[NR_CPUS] __cacheline_aligned = {{0}};
+static DEFINE_PER_CPU(int, sockets_in_use);
/*
* Support routines. Move socket addresses back and forth across the kernel/user
@@ -475,7 +472,8 @@
inode->i_uid = current->fsuid;
inode->i_gid = current->fsgid;
- sockets_in_use[smp_processor_id()].counter++;
+ get_cpu_var(sockets_in_use)++;
+ put_cpu_var(sockets_in_use);
return sock;
}
@@ -511,7 +509,8 @@
if (sock->fasync_list)
printk(KERN_ERR "sock_release: fasync list not empty!\n");
- sockets_in_use[smp_processor_id()].counter--;
+ get_cpu_var(sockets_in_use)--;
+ put_cpu_var(sockets_in_use);
if (!sock->file) {
iput(SOCK_INODE(sock));
return;
@@ -1851,7 +1850,7 @@
int counter = 0;
for (cpu = 0; cpu < NR_CPUS; cpu++)
- counter += sockets_in_use[cpu].counter;
+ counter += per_cpu(sockets_in_use, cpu);
/* It can be negative, by the way. 8) */
if (counter < 0)
next reply other threads:[~2002-12-23 13:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-23 13:38 Ravikiran G Thirumalai [this message]
2002-12-23 20:16 ` [patch] Convert sockets_in_use to use per_cpu areas David S. Miller
2002-12-24 0:00 ` Chris Wedgwood
2002-12-24 0:23 ` David S. Miller
2002-12-24 6:48 ` Ravikiran G Thirumalai
2002-12-24 6:50 ` David S. Miller
2003-01-07 9:16 ` David S. Miller
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=20021223190847.G23413@in.ibm.com \
--to=kiran@in.ibm.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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