| To: | Krishna Kumar <kumarkr@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH]snmp6 64-bit counter support in proc.c |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Wed, 28 Jan 2004 11:33:36 -0800 |
| Cc: | kuznet@xxxxxxxxxxxxx, mashirle@xxxxxxxxxx, netdev@xxxxxxxxxxx, xma@xxxxxxxxxx |
| In-reply-to: | <OFB07FA138.DADDB14B-ON88256E29.00692BAE@us.ibm.com> |
| References: | <OFB07FA138.DADDB14B-ON88256E29.00692BAE@us.ibm.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Wed, 28 Jan 2004 11:19:36 -0800 Krishna Kumar <kumarkr@xxxxxxxxxx> wrote: [ ... idea to use seq locks ] > Does that sound better ? Well, I thought the goal was to move the expensive part of doing this out of the writers, which we assume will exceed readers. Seq locks favor readers, and assume that the write is the less common operation. Putting seq locks around every stat counter bump is going to plump up the code a lot. Maybe your idea and original assumption are fine, in essence we live with this now, don't we? :-) Perhaps there are some better ideas? |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH]snmp6 64-bit counter support in proc.c, Krishna Kumar |
|---|---|
| Next by Date: | Re: NAT before IPsec with 2.6, David S. Miller |
| Previous by Thread: | Re: [PATCH]snmp6 64-bit counter support in proc.c, Krishna Kumar |
| Next by Thread: | Re: [PATCH]snmp6 64-bit counter support in proc.c, Shirley Ma |
| Indexes: | [Date] [Thread] [Top] [All Lists] |