Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Alexander Duyck <alexander.h.duyck@intel.com>,
	Brattain <ross.b.brattain@intel.com>,
	Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: [RFC] ixgbe: is DCA really that good ?
Date: Wed, 06 Apr 2011 15:44:04 +0200	[thread overview]
Message-ID: <1302097444.3209.85.camel@edumazet-laptop> (raw)

Hi guys


In a forwarding [or RPS/RFS] setup, why should we populate cpu caches
with full frames content ? We only need first cache line to perform
routing [or RPS/RFS] decision.

-> DCA should be a knob (ethtool ?) that an admin can switch off and on,
port by port, not a CONFIG_IXGBE_DCA thing.

Thanks



             reply	other threads:[~2011-04-06 13:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-06 13:44 Eric Dumazet [this message]
2011-04-06 15:24 ` [RFC] ixgbe: is DCA really that good ? Tom Herbert
2011-04-06 16:14   ` Eric Dumazet
2011-04-06 17:05 ` Alexander Duyck

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=1302097444.3209.85.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=alexander.h.duyck@intel.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=ross.b.brattain@intel.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