From: "David S. Miller" <davem@davemloft.net>
To: christoph@lameter.com
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
shai@scalex86.org, akpm@osdl.org, netdev@vger.kernel.org,
herbert@gondor.apana.org.au
Subject: Re: [PATCH] dst_entry structure use,lastuse and refcnt abstraction
Date: Thu, 23 Jun 2005 20:36:47 -0700 (PDT) [thread overview]
Message-ID: <20050623.203647.88475017.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.62.0506231953260.28244@graphe.net>
From: Christoph Lameter <christoph@lameter.com>
Date: Thu, 23 Jun 2005 20:04:52 -0700 (PDT)
> The patch also removes the atomic_dec_and_test in dst_destroy.
That is the only part of this patch I'm willing to entertain
at this time, as long as Herbert Xu ACKs it. How much of that
quoted %3 gain does this change alone give you?
Also, please post networking patches to netdev@vger.kernel.org.
Because you didn't, the majority of the networking maintainers
did not see your dst patch submissions. It's mentioned in
linux/MAINTAINERS for a reason:
NETWORKING [GENERAL]
P: Networking Team
M: netdev@vger.kernel.org
L: netdev@vger.kernel.org
S: Maintained
Thanks.
next parent reply other threads:[~2005-06-24 3:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.62.0506231953260.28244@graphe.net>
2005-06-24 3:36 ` David S. Miller [this message]
2005-06-24 3:40 ` [PATCH] dst_entry structure use,lastuse and refcnt abstraction Christoph Lameter
2005-06-24 3:47 ` David S. Miller
2005-06-24 3:49 ` Christoph Lameter
2005-06-24 3:54 ` David S. Miller
2005-06-24 4:06 ` Christoph Lameter
2005-06-24 4:11 ` David S. Miller
2005-06-24 6:03 ` Christoph Lameter
2005-06-24 6:16 ` David S. Miller
2005-06-24 10:57 ` [PATCH] bugfix and scalability changes in net/ipv4/route.c Eric Dumazet
2005-06-28 20:14 ` David S. Miller
[not found] ` <Pine.LNX.4.62.0506232005030.28244@graphe.net>
2005-06-24 4:58 ` [PATCH] dst numa: Avoid dst counter cacheline bouncing Dipankar Sarma
2005-06-24 5:05 ` Christoph Lameter
2005-06-24 7:29 ` Dipankar Sarma
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=20050623.203647.88475017.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=christoph@lameter.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shai@scalex86.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 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).