From: David Miller <davem@davemloft.net>
To: mst@redhat.com
Cc: linux-kernel@vger.kernel.org, john.fastabend@gmail.com,
jakub.kicinski@netronome.com, xiyou.wangcong@gmail.com,
jiri@resnulli.us, netdev@vger.kernel.org, jasowang@redhat.com
Subject: Re: [PATCH] ptr_ring: document usage around __ptr_ring_peek
Date: Mon, 15 Jan 2018 13:19:32 -0500 (EST) [thread overview]
Message-ID: <20180115.131932.478466552170808819.davem@davemloft.net> (raw)
In-Reply-To: <1515592856-16578-1-git-send-email-mst@redhat.com>
From: "Michael S. Tsirkin" <mst@redhat.com>
Date: Wed, 10 Jan 2018 16:03:05 +0200
> This explains why is the net usage of __ptr_ring_peek
> actually ok without locks.
>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Applied, thanks Michael.
prev parent reply other threads:[~2018-01-15 18:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 14:03 [PATCH] ptr_ring: document usage around __ptr_ring_peek Michael S. Tsirkin
2018-01-10 18:15 ` John Fastabend
2018-01-15 18:19 ` 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=20180115.131932.478466552170808819.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=jasowang@redhat.com \
--cc=jiri@resnulli.us \
--cc=john.fastabend@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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).