qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Cornelia Huck <cohuck@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	qemu devel list <qemu-devel@nongnu.org>,
	Yuval Shaia <yuval.shaia.ml@gmail.com>
Subject: Re: [PATCH RFC] pvrdma: wean code off pvrdma_ring.h kernel header
Date: Mon, 22 Feb 2021 03:40:06 -0500 (EST)	[thread overview]
Message-ID: <1306072831.56396199.1613983206292.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAC_L=vVoqVdetQfxDdvb=v9einKj+mhNs=p7Vybh1D6OgR1FvQ@mail.gmail.com>



----- 原始邮件 -----
> Hi Jason.
> 
> On Tue, Feb 9, 2021 at 5:47 AM Jason Wang <jasowang@redhat.com> wrote:
> 
> >
> > On 2021/2/9 上午1:28, Paolo Bonzini wrote:
> > > On 08/02/21 18:17, Cornelia Huck wrote:
> > >> On Fri, 29 Jan 2021 16:27:19 +0100
> > >> Cornelia Huck <cohuck@redhat.com> wrote:
> > >>
> > >>> On Fri, 22 Jan 2021 19:00:29 +0100
> > >>> Cornelia Huck <cohuck@redhat.com> wrote:
> > >>>
> > >>>> The pvrdma code relies on the pvrdma_ring.h kernel header for some
> > >>>> basic ring buffer handling. The content of that header isn't very
> > >>>> exciting, but contains some (q)atomic_*() invocations that (a)
> > >>>> cause manual massaging when doing a headers update, and (b) are
> > >>>> an indication that we probably should not be importing that header
> > >>>> at all.
> > >>>>
> > >>>> Let's reimplement the ring buffer handling directly in the pvrdma
> > >>>> code instead. This arguably also improves readability of the code.
> > >>>>
> > >>>> Importing the header can now be dropped.
> > >>>>
> > >>>> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> > >>>> ---
> > >>>>
> > >>>> Compile-tested only, needs both testing and more eyeballs :)
> > >>>
> > >>> Friendly ping :)
> > >>>
> > >>> Suggestions for a test setup to do some sanity checks (that does not
> > >>> require special hardware) also welcome.
> > >>
> > >> Can I interest anyone in this? I'd be happy doing sanity tests myself,
> > >> but I have a hard time figuring out even where to start...
> > >
> > > Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
> > >
> > > Jason, Michael, are you going to pick this up?
> > >
> > > Paolo
> >
> >
> > I will queue this.
> >
> 
> 
> Have you picked it up? It will be great so I'll not send a PR with a single
> patch...
> BTW, Yuval tested and acked the patch.

Plan to send a pull request this Friday.

It should be part of that.

Thanks

> 
> Thanks,
> Marcel
> 
> [...]
> 
> 
> >
> >
> 



  reply	other threads:[~2021-02-22  8:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 18:00 [PATCH RFC] pvrdma: wean code off pvrdma_ring.h kernel header Cornelia Huck
2021-01-29 15:27 ` Cornelia Huck
2021-02-08 17:17   ` Cornelia Huck
2021-02-08 17:28     ` Paolo Bonzini
2021-02-09  3:47       ` Jason Wang
2021-02-22  8:33         ` Marcel Apfelbaum
2021-02-22  8:40           ` Jason Wang [this message]
2021-02-08 18:29 ` Michael S. Tsirkin
2021-02-09  7:40   ` Cornelia Huck
2021-02-10  8:56 ` Yuval Shaia

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=1306072831.56396199.1613983206292.JavaMail.zimbra@redhat.com \
    --to=jasowang@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yuval.shaia.ml@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).