From: Roman Kagan <rkagan@virtuozzo.com>
To: "linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>
Subject: flow control in vmbus ring buffers
Date: Tue, 24 Dec 2019 10:56:08 +0000 [thread overview]
Message-ID: <20191224105605.GA164618@rkaganb.sw.ru> (raw)
I'm trying to get my head around how the flow control in vmbus ring
buffers works.
In particular, I'm failing to see how the following can be prevented:
producer | consumer
==================================================================
read read_index |
(enough room for packet) |
write pending_send_sz = 0 |
write packet |
update write_index |
| read write_index
read read_index | read packet
(not enough room for packet) | update read_index (= write_index)
| read pending_send_sz = 0
write pending_send_sz = X | skip notification
go to sleep | go to sleep
stall
Could anybody please shed some light on how it's supposed to work?
Thanks,
Roman.
next reply other threads:[~2019-12-24 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-24 10:56 Roman Kagan [this message]
2019-12-24 16:28 ` flow control in vmbus ring buffers Roman Kagan
2019-12-24 18:03 ` Michael Kelley
2019-12-25 8:46 ` Roman Kagan
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=20191224105605.GA164618@rkaganb.sw.ru \
--to=rkagan@virtuozzo.com \
--cc=linux-hyperv@vger.kernel.org \
/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