From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Shivam Kumar <shivam.kumar1@nutanix.com>,
kvm@vger.kernel.org, agraf@csgraf.de
Subject: Re: [PATCH v2 0/1] KVM: Dirty quota-based throttling
Date: Tue, 8 Mar 2022 15:53:06 +0000 [thread overview]
Message-ID: <Yid74seFMjB49FIZ@google.com> (raw)
In-Reply-To: <76606ce7-6bbf-dc92-af2c-ee3e54169ecd@redhat.com>
On Tue, Mar 08, 2022, Paolo Bonzini wrote:
> On 1/5/22 16:39, Shivam Kumar wrote:
> >
> > > On Mon, Jan 03, 2022, Shivam Kumar wrote:
> > > > I would be grateful if I could receive some feedback on the
> > > > dirty quota v2
> > > > patchset.
> > > 'Twas the week before Christmas, when all through the list,
> > > not a reviewer was stirring, not even a twit.
> > >
> > > There's a reason I got into programming and not literature.
> > > Anyways, your patch
> > > is in the review queue, it'll just be a few days/weeks. :-)
> > Thank you so much Sean for the update!
>
> Hi, are you going to send v3?
https://lore.kernel.org/all/20220306220849.215358-1-shivam.kumar1@nutanix.com
next prev parent reply other threads:[~2022-03-08 15:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 5:57 [PATCH v2 0/1] KVM: Dirty quota-based throttling Shivam Kumar
2021-12-20 5:57 ` [PATCH v2 1/1] KVM: Implement dirty quota-based throttling of vcpus Shivam Kumar
2022-01-10 18:08 ` Sean Christopherson
[not found] ` <eca3faed-5f2c-6217-fb2c-298855510265@nutanix.com>
2022-01-11 16:59 ` Sean Christopherson
2022-01-23 18:58 ` Shivam Kumar
2022-01-26 21:04 ` Sean Christopherson
2022-01-03 8:46 ` [PATCH v2 0/1] KVM: Dirty quota-based throttling Shivam Kumar
2022-01-04 17:01 ` Sean Christopherson
2022-01-05 15:39 ` Shivam Kumar
2022-03-08 14:59 ` Paolo Bonzini
2022-03-08 15:53 ` Sean Christopherson [this message]
2022-03-08 18:22 ` Shivam Kumar
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=Yid74seFMjB49FIZ@google.com \
--to=seanjc@google.com \
--cc=agraf@csgraf.de \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=shivam.kumar1@nutanix.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).