From: David Miller <davem@davemloft.net>
To: brouer@redhat.com
Cc: eric.dumazet@gmail.com, fw@strlen.de, netdev@vger.kernel.org,
pablo@netfilter.org, amwang@redhat.com, kaber@trash.net,
herbert@gondor.hengli.com.au, dborkman@redhat.com
Subject: Re: [net-next PATCH V2 0/6] net: frag performance tuning cachelines for NUMA/SMP systems
Date: Tue, 29 Jan 2013 13:38:25 -0500 (EST) [thread overview]
Message-ID: <20130129.133825.2102060433138975917.davem@davemloft.net> (raw)
In-Reply-To: <20130129094331.13513.28377.stgit@dragon>
From: Jesper Dangaard Brouer <brouer@redhat.com>
Date: Tue, 29 Jan 2013 10:44:01 +0100
> This patchset is V2, with some trivial code fixes, which were noticed
> by DaveM. It is still a partly respin of my fragmentation optimization
> patches: http://thread.gmane.org/gmane.linux.network/250914
Series applied, thanks Jesper.
prev parent reply other threads:[~2013-01-29 18:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 9:44 [net-next PATCH V2 0/6] net: frag performance tuning cachelines for NUMA/SMP systems Jesper Dangaard Brouer
2013-01-29 9:44 ` [net-next PATCH V2 1/6] net: cacheline adjust struct netns_frags for better frag performance Jesper Dangaard Brouer
2013-01-29 9:44 ` [net-next PATCH V2 2/6] net: cacheline adjust struct inet_frags " Jesper Dangaard Brouer
2013-01-29 9:44 ` [net-next PATCH V2 3/6] net: cacheline adjust struct inet_frag_queue Jesper Dangaard Brouer
2013-01-29 9:45 ` [net-next PATCH V2 4/6] net: frag helper functions for mem limit tracking Jesper Dangaard Brouer
2013-01-29 9:45 ` [net-next PATCH V2 5/6] net: use lib/percpu_counter API for fragmentation mem accounting Jesper Dangaard Brouer
2013-01-29 9:45 ` [net-next PATCH V2 6/6] net: frag, move LRU list maintenance outside of rwlock Jesper Dangaard Brouer
2013-01-29 18:38 ` David Miller [this message]
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=20130129.133825.2102060433138975917.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=amwang@redhat.com \
--cc=brouer@redhat.com \
--cc=dborkman@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=fw@strlen.de \
--cc=herbert@gondor.hengli.com.au \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.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).