From: "manish.mishra" <manish.mishra@nutanix.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, berrange@redhat.com,
prerna.saxena@nutanix.com, quintela@redhat.com,
dgilbert@redhat.com, lsoaresp@redhat.com
Subject: Re: [PATCH v5 1/2] io: Add support for MSG_PEEK for socket channel
Date: Tue, 29 Nov 2022 16:24:58 +0530 [thread overview]
Message-ID: <aaf17b45-ea8a-cd93-008c-b43b68532ef1@nutanix.com> (raw)
In-Reply-To: <Y35gyiCk/Kjdd1Lq@x1n>
On 23/11/22 11:34 pm, Peter Xu wrote:
> On Wed, Nov 23, 2022 at 05:27:34PM +0000, manish.mishra wrote:
>> MSG_PEEK reads from the peek of channel, The data is treated as
>> unread and the next read shall still return this data. This
>> support is currently added only for socket class. Extra parameter
>> 'flags' is added to io_readv calls to pass extra read flags like
>> MSG_PEEK.
>>
>> Reviewed-by: Daniel P. Berrangé <berrange@redhat.co
>> Suggested-by: Daniel P. Berrangé <berrange@redhat.com
>> Signed-off-by: manish.mishra <manish.mishra@nutanix.com>
> Reviewed-by: Peter Xu <peterx@redhat.com>
>
Hi Peter, Daniel
Just wanted to check if both patches in this series are approved or i need to update few more things. Also Peter, for your Review-by to be included do i need to send another patch version or it will be taken up whoever will be merging it?
Thanks
Manish Mishra
next prev parent reply other threads:[~2022-11-29 10:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 17:27 [PATCH v5 0/2] check magic value for deciding the mapping of channels manish.mishra
2022-11-23 17:27 ` [PATCH v5 1/2] io: Add support for MSG_PEEK for socket channel manish.mishra
2022-11-23 18:04 ` Peter Xu
2022-11-29 10:54 ` manish.mishra [this message]
2022-11-29 14:27 ` Peter Xu
2022-11-29 14:38 ` manish.mishra
2022-12-13 20:37 ` Peter Xu
2022-11-23 17:27 ` [PATCH v5 2/2] migration: check magic value for deciding the mapping of channels manish.mishra
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=aaf17b45-ea8a-cd93-008c-b43b68532ef1@nutanix.com \
--to=manish.mishra@nutanix.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lsoaresp@redhat.com \
--cc=peterx@redhat.com \
--cc=prerna.saxena@nutanix.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).