On 2017年11月29日 02:06, Michael S. Tsirkin wrote:
On Tue, Nov 28, 2017 at 03:46:44PM +0200, Victor Kaplansky wrote:
From: Victor Kaplansky
If we allow qemu to change logging area after it was already established,
it may require from the backend to acquire a lock on each access to
the log_base,
> From: "Michael S. Tsirkin"
> To: "Victor Kaplansky"
> Cc: qemu-devel@nongnu.org, "Maxime Coquelin" ,
> "Jason Wang"
> Sent: Tuesday, November 28, 2017 8:45:43 PM
> Subject: Re: [PATCH] vhost-user spec: Clarify policy on setting log_base
>
> On Tue, Nov 28, 2017 at 01:34:19PM -0500, Victor Ka
On Tue, Nov 28, 2017 at 01:34:19PM -0500, Victor Kaplansky wrote:
> > From: "Michael S. Tsirkin"
> > To: "Victor Kaplansky"
> > Cc: qemu-devel@nongnu.org, "Maxime Coquelin" ,
> > "Jason Wang"
> > Sent: Tuesday, November 28, 2017 8:06:52 PM
> > Subject: Re: [PATCH] vhost-user spec: Clarify polic
> From: "Michael S. Tsirkin"
> To: "Victor Kaplansky"
> Cc: qemu-devel@nongnu.org, "Maxime Coquelin" ,
> "Jason Wang"
> Sent: Tuesday, November 28, 2017 8:06:52 PM
> Subject: Re: [PATCH] vhost-user spec: Clarify policy on setting log_base
>
> On Tue, Nov 28, 2017 at 03:46:44PM +0200, Victor Ka
el@nongnu.org,
> > > "Maxime Coquelin"
> > > Sent: Tuesday, November 28, 2017 6:12:44 PM
> > > Subject: Re: [Qemu-devel] [PATCH] vhost-user spec: Clarify policy on
> > > setting log_base
> > >
> > > On Tue, Nov 28, 2017 at 04:04:21PM +
On Tue, Nov 28, 2017 at 03:46:44PM +0200, Victor Kaplansky wrote:
> From: Victor Kaplansky
>
> If we allow qemu to change logging area after it was already established,
> it may require from the backend to acquire a lock on each access to
> the log_base, which has a potential quite a big performa
On Tue, Nov 28, 2017 at 12:29:04PM -0500, Victor Kaplansky wrote:
> > From: "Michael S. Tsirkin"
> > To: "Victor Kaplansky"
> > Cc: qemu-devel@nongnu.org, "Maxime Coquelin"
> > Sent: Tuesday, November 28, 2017 6:16:32 PM
> > Subject: Re: [PATCH] vhost-user spec: Clarify policy on setting log_bas
> > +Note that master is not expected to issue more than one
> > VHOST_USER_SET_LOG_BASE
> > +request before the rings are fully stopped by the master. Thus no
> > modifications
> > +to log_base address are allowed before the rings are restated and the
> > client
> > +can ignore all subsequent VHOS
* Victor Kaplansky (vkapl...@redhat.com) wrote:
> > From: "Michael S. Tsirkin"
> > To: "Dr. David Alan Gilbert"
> > Cc: "Victor Kaplansky" , qemu-devel@nongnu.org,
> > "Maxime Coquelin"
> > Sent: Tuesday, November 28,
> From: "Michael S. Tsirkin"
> To: "Dr. David Alan Gilbert"
> Cc: "Victor Kaplansky" , qemu-devel@nongnu.org, "Maxime
> Coquelin"
> Sent: Tuesday, November 28, 2017 6:12:44 PM
> Subject: Re: [Qemu-devel] [PATCH] vhost-user spec: Clari
> From: "Michael S. Tsirkin"
> To: "Victor Kaplansky"
> Cc: qemu-devel@nongnu.org, "Maxime Coquelin"
> Sent: Tuesday, November 28, 2017 6:16:32 PM
> Subject: Re: [PATCH] vhost-user spec: Clarify policy on setting log_base
>
> On Tue, Nov 28, 2017 at 03:46:44PM +0200, Victor Kaplansky wrote:
> >
On Tue, Nov 28, 2017 at 03:46:44PM +0200, Victor Kaplansky wrote:
> From: Victor Kaplansky
>
> If we allow qemu to change logging area after it was already established,
> it may require from the backend to acquire a lock on each access to
> the log_base, which has a potential quite a big performa
On Tue, Nov 28, 2017 at 04:04:21PM +, Dr. David Alan Gilbert wrote:
> * Victor Kaplansky (vkapl...@redhat.com) wrote:
> > From: Victor Kaplansky
> >
> > If we allow qemu to change logging area after it was already established,
> > it may require from the backend to acquire a lock on each acce
* Victor Kaplansky (vkapl...@redhat.com) wrote:
> From: Victor Kaplansky
>
> If we allow qemu to change logging area after it was already established,
> it may require from the backend to acquire a lock on each access to
> the log_base, which has a potential quite a big performance hit.
>
> Thus
From: Victor Kaplansky
If we allow qemu to change logging area after it was already established,
it may require from the backend to acquire a lock on each access to
the log_base, which has a potential quite a big performance hit.
Thus we would like to clarify in the spec, that qemu is not expect
15 matches
Mail list logo
