From: Bharat Bhushan <bbhushan2@marvell.com>
To: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<sgoutham@marvell.com>, <gakula@marvell.com>,
<sbhatta@marvell.com>, <hkelam@marvell.com>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <jerinj@marvell.com>, <lcherian@marvell.com>,
<richardcochran@gmail.com>, <bbhushan2@marvell.com>,
b@mx0a-0016f401.pphosted.com
Subject: [net-next,v6 1/8] octeontx2-pf: map skb data as device writeable
Date: Mon, 19 Aug 2024 17:53:41 +0530 [thread overview]
Message-ID: <20240819122348.490445-2-bbhushan2@marvell.com> (raw)
In-Reply-To: <20240819122348.490445-1-bbhushan2@marvell.com>
Crypto hardware need write permission for in-place encrypt
or decrypt operation on skb-data to support IPsec crypto
offload. So map this memory as device read-write.
Signed-off-by: Bharat Bhushan <bbhushan2@marvell.com>
---
drivers/net/ethernet/marvell/octeontx2/nic/otx2_txrx.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/marvell/octeontx2/nic/otx2_txrx.c b/drivers/net/ethernet/marvell/octeontx2/nic/otx2_txrx.c
index 3eb85949677a..ce1a7db745c5 100644
--- a/drivers/net/ethernet/marvell/octeontx2/nic/otx2_txrx.c
+++ b/drivers/net/ethernet/marvell/octeontx2/nic/otx2_txrx.c
@@ -98,7 +98,7 @@ static dma_addr_t otx2_dma_map_skb_frag(struct otx2_nic *pfvf,
offset = skb_frag_off(frag);
*len = skb_frag_size(frag);
}
- return otx2_dma_map_page(pfvf, page, offset, *len, DMA_TO_DEVICE);
+ return otx2_dma_map_page(pfvf, page, offset, *len, DMA_BIDIRECTIONAL);
}
static void otx2_dma_unmap_skb_frags(struct otx2_nic *pfvf, struct sg_list *sg)
@@ -107,7 +107,7 @@ static void otx2_dma_unmap_skb_frags(struct otx2_nic *pfvf, struct sg_list *sg)
for (seg = 0; seg < sg->num_segs; seg++) {
otx2_dma_unmap_page(pfvf, sg->dma_addr[seg],
- sg->size[seg], DMA_TO_DEVICE);
+ sg->size[seg], DMA_BIDIRECTIONAL);
}
sg->num_segs = 0;
}
--
2.34.1
next prev parent reply other threads:[~2024-08-19 12:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 12:23 [net-next,v6 0/8] cn10k-ipsec: Add outbound inline ipsec support Bharat Bhushan
2024-08-19 12:23 ` Bharat Bhushan [this message]
2024-08-20 22:35 ` [net-next,v6 1/8] octeontx2-pf: map skb data as device writeable Jakub Kicinski
2024-08-22 3:45 ` Bharat Bhushan
2024-08-22 14:48 ` Jakub Kicinski
2024-08-23 11:25 ` Bharat Bhushan
2024-08-24 13:59 ` Bharat Bhushan
2024-08-19 12:23 ` [net-next,v6 2/8] octeontx2-pf: Move skb fragment map/unmap to common code Bharat Bhushan
2024-08-19 12:23 ` [net-next,v6 3/8] octeontx2-af: Disable backpressure between CPT and NIX Bharat Bhushan
2024-08-19 12:23 ` [net-next,v6 4/8] cn10k-ipsec: Init hardware for outbound ipsec crypto offload Bharat Bhushan
2024-08-19 12:23 ` [net-next,v6 5/8] cn10k-ipsec: Add SA add/del support for outb " Bharat Bhushan
2024-08-19 12:23 ` [net-next,v6 6/8] cn10k-ipsec: Process outbound " Bharat Bhushan
2024-08-19 12:23 ` [net-next,v6 7/8] cn10k-ipsec: Allow ipsec crypto offload for skb with SA Bharat Bhushan
2024-08-19 12:23 ` [net-next,v6 8/8] cn10k-ipsec: Enable outbound ipsec crypto offload Bharat Bhushan
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=20240819122348.490445-2-bbhushan2@marvell.com \
--to=bbhushan2@marvell.com \
--cc=b@mx0a-0016f401.pphosted.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jerinj@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.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
all inboxes | Powered by JetHome®