From: David Miller <davem@davemloft.net>
To: jakub.kicinski@netronome.com
Cc: netdev@vger.kernel.org, kubakici@wp.pl, oss-drivers@netronome.com
Subject: Re: [PATCH net-next v3 0/5] nfp: DMA flags, adjust head and fixes
Date: Mon, 24 Apr 2017 14:36:04 -0400 (EDT) [thread overview]
Message-ID: <20170424.143604.1133862806777963968.davem@davemloft.net> (raw)
In-Reply-To: <20170423031756.94429-1-jakub.kicinski@netronome.com>
From: Jakub Kicinski <jakub.kicinski@netronome.com>
Date: Sat, 22 Apr 2017 20:17:51 -0700
> This series takes advantage of Alex's DMA_ATTR_SKIP_CPU_SYNC to make
> XDP packet modifications "correct" from DMA API point of view. It
> also allows us to parse the metadata before we run XDP at no additional
> DMA sync cost. That way we can get rid of the metadata memcpy, and
> remove the last upstream user of bpf_prog->xdp_adjust_head.
>
> David's patch adds a way to read capabilities from the management
> firmware.
>
> There are also two net-next fixes. Patch 4 which fixes what seems to
> be a result of a botched rebase on my part. Patch 5 corrects locking
> when state of ethernet ports is being refreshed.
>
> ---
> v3: move the sync from alloc func to the actual give to hw func
> v2: sync rx buffers before giving them to the card (Alex)
Series applied, thanks Jakub.
prev parent reply other threads:[~2017-04-24 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-23 3:17 [PATCH net-next v3 0/5] nfp: DMA flags, adjust head and fixes Jakub Kicinski
2017-04-23 3:17 ` [PATCH net-next v3 1/5] nfp: make use of the DMA_ATTR_SKIP_CPU_SYNC attr Jakub Kicinski
2017-04-23 3:17 ` [PATCH net-next v3 2/5] nfp: parse metadata prepend before XDP runs Jakub Kicinski
2017-04-23 3:17 ` [PATCH net-next v3 3/5] nfp: add NSP routine to get static information Jakub Kicinski
2017-04-23 3:17 ` [PATCH net-next v3 4/5] nfp: fix free list buffer size reporting Jakub Kicinski
2017-04-23 3:17 ` [PATCH net-next v3 5/5] nfp: remove the refresh of all ports optimization Jakub Kicinski
2017-04-24 18:36 ` 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=20170424.143604.1133862806777963968.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=kubakici@wp.pl \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.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).