netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: felix.manlunas@cavium.com
Cc: netdev@vger.kernel.org, raghu.vatsavayi@cavium.com,
	derek.chickles@cavium.com, satananda.burla@cavium.com,
	prasad.kanneganti@cavium.com
Subject: Re: [PATCH net-next] liquidio: replace info-pointer mode with buffer-pointer-only mode
Date: Sun, 18 Jun 2017 23:55:59 -0400 (EDT)	[thread overview]
Message-ID: <20170618.235559.1148715988392937305.davem@davemloft.net> (raw)
In-Reply-To: <20170618120411.GA1401@felix-thinkpad.cavium.com>

From: Felix Manlunas <felix.manlunas@cavium.com>
Date: Sun, 18 Jun 2017 05:04:11 -0700

> From: Prasad Kanneganti <prasad.kanneganti@cavium.com>
> 
> Each Octeon output ring can DMA packets to host memory in two modes:  info-
> pointer mode and buffer-pointer-only mode.  In info-pointer mode, Octeon
> takes two buffer pointers for each packet and places the length of the
> packet along with specified number of bytes from the beginning of the
> packet into one buffer and the rest of the packet in a separate buffer.  In
> buffer-pointer-only mode, Octeon takes single buffer pointer and places the
> length of the packet at the beginning of the buffer followed by the packet
> data.
> 
> This patch switches all Octeon output rings from info-pointer mode to
> buffer-pointer-only mode.  This results in fewer DMA setups and cache line
> snoops.
> 
> Signed-off-by: Prasad Kanneganti <pkanneganti@cavium.com>
> Signed-off-by: Derek Chickles <derek.chickles@cavium.com>
> Signed-off-by: Satanand Burla <satananda.burla@cavium.com>
> Signed-off-by: Felix Manlunas <felix.manlunas@cavium.com>

Applied.

      reply	other threads:[~2017-06-19  3:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-18 12:04 [PATCH net-next] liquidio: replace info-pointer mode with buffer-pointer-only mode Felix Manlunas
2017-06-19  3:55 ` 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=20170618.235559.1148715988392937305.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=derek.chickles@cavium.com \
    --cc=felix.manlunas@cavium.com \
    --cc=netdev@vger.kernel.org \
    --cc=prasad.kanneganti@cavium.com \
    --cc=raghu.vatsavayi@cavium.com \
    --cc=satananda.burla@cavium.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;
as well as URLs for NNTP newsgroup(s).