From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Kiran Kumar <kkokkilagadda@caviumnetworks.com>,
jerin.jacob@caviumnetworks.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] kni: fix kni Rx fifo producer synchronization
Date: Mon, 27 Aug 2018 15:07:35 +0100 [thread overview]
Message-ID: <649064d2-430c-d761-44ce-453e1a14031a@intel.com> (raw)
In-Reply-To: <1534413317-644-1-git-send-email-kkokkilagadda@caviumnetworks.com>
On 8/16/2018 10:55 AM, Kiran Kumar wrote:
> With existing code in kni_fifo_put, rx_q values are not being updated
> before updating fifo_write. While reading rx_q in kni_net_rx_normal,
> This is causing the sync issue on other core. So adding a write
> barrier to make sure the values being synced before updating fifo_write.
>
> Fixes: 3fc5ca2f6352 ("kni: initial import")
>
> Signed-off-by: Kiran Kumar <kkokkilagadda@caviumnetworks.com>
> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2018-08-27 14:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 10:23 [dpdk-dev] [PATCH] kni: fix kni rx " Kiran Kumar
2018-08-09 11:30 ` Ferruh Yigit
2018-08-16 6:52 ` Jerin Jacob
2018-08-16 12:28 ` Ferruh Yigit
2018-08-16 9:01 ` Jerin Jacob
2018-08-16 9:55 ` [dpdk-dev] [PATCH v2] kni: fix kni Rx " Kiran Kumar
2018-08-27 14:07 ` Ferruh Yigit [this message]
2018-08-27 15:40 ` Gavin Hu
2018-08-28 10:43 ` Kokkilagadda, Kiran
2018-08-28 10:51 ` Kokkilagadda, Kiran
2018-08-28 19:30 ` Gavin Hu
2018-08-29 4:59 ` Honnappa Nagarahalli
2018-08-29 5:49 ` Kokkilagadda, Kiran
2018-08-29 7:34 ` Ola Liljedahl
2018-08-29 8:28 ` Jerin Jacob
2018-08-29 8:47 ` Ola Liljedahl
2018-08-29 8:57 ` Jerin Jacob
2018-09-13 17:40 ` Honnappa Nagarahalli
2018-09-13 17:51 ` Jerin Jacob
2018-09-13 23:45 ` Honnappa Nagarahalli
2018-09-14 2:45 ` Jerin Jacob
2018-09-18 15:53 ` Ferruh Yigit
2018-09-19 5:37 ` Honnappa Nagarahalli
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=649064d2-430c-d761-44ce-453e1a14031a@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=kkokkilagadda@caviumnetworks.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).