From: Joe Perches <joe@perches.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] net: add a prefetch in socket backlog processing
Date: Tue, 01 May 2012 06:09:17 -0700 [thread overview]
Message-ID: <1335877757.26217.67.camel@joe2Laptop> (raw)
In-Reply-To: <1335875351.11396.55.camel@edumazet-glaptop>
On Tue, 2012-05-01 at 14:29 +0200, Eric Dumazet wrote:
> On Tue, 2012-05-01 at 04:52 -0700, Joe Perches wrote:
>
> > That's true for cpus with sufficient cache but prefetch
> > might be wasteful for cpus without (like some ARMs).
> >
> > Some of the sk_backlog_rcv functions like tcp_v4_do_rcv
> > can be relatively large.
>
> You speak of icache here. Thats different matter.
>
> My patch does a prefetch of data (dcache)
Actually I meant cpus with an integrated cache
like the old arm 710 and the sh3/7710.
I think those are still possible compilation
targets, but perhaps no one cares anymore.
> How this prefetch() is different than other ones in kernel ?
I'm not suggesting prefetch isn't useful.
If prefetch improves performance for the general case
it's good. If the prefetch can also be trivially
compile time wrapped to not impact older supported
targets, I think that's good too.
> For old cpus, you can use linux 2.4 it works much better.
Deprecating older targets may not be a bad thing either.
cheers, Joe
next prev parent reply other threads:[~2012-05-01 13:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 2:07 [PATCH net-next] net: add a prefetch in socket backlog processing Eric Dumazet
2012-05-01 3:24 ` Joe Perches
2012-05-01 6:34 ` Eric Dumazet
2012-05-01 6:42 ` Eric Dumazet
2012-05-01 11:52 ` Joe Perches
2012-05-01 12:29 ` Eric Dumazet
2012-05-01 13:09 ` Joe Perches [this message]
2012-05-01 13:41 ` David 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=1335877757.26217.67.camel@joe2Laptop \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox