On Mon, 2015-11-16 at 18:36 +, Wei Liu wrote:
Ian, were your concerns addressed by this threadlet?
> On Mon, Nov 16, 2015 at 06:09:54PM +, Ian Jackson wrote:
> > Andrew Cooper writes ("Re: [PATCH] cxenstored: correct calculation of
> > data/space in the ring"):
> > > On 16/11/15 18:01, Ia
On Mon, Nov 16, 2015 at 06:09:54PM +, Ian Jackson wrote:
> Andrew Cooper writes ("Re: [PATCH] cxenstored: correct calculation of
> data/space in the ring"):
> > On 16/11/15 18:01, Ian Jackson wrote:
> > > Wei Liu writes ("[PATCH] cxenstored: correct calculation of data/space in
> > > the ring
Andrew Cooper writes ("Re: [PATCH] cxenstored: correct calculation of
data/space in the ring"):
> On 16/11/15 18:01, Ian Jackson wrote:
> > Wei Liu writes ("[PATCH] cxenstored: correct calculation of data/space in
> > the ring"):
> >> The cxenstored implementation can't handle cross ring boundary
On 16/11/15 18:01, Ian Jackson wrote:
> Wei Liu writes ("[PATCH] cxenstored: correct calculation of data/space in the
> ring"):
>> The cxenstored implementation can't handle cross ring boundary read and
>> write. It gets aways with buggy behaviour because upper layer won't
>> sleep when short-writ
Wei Liu writes ("[PATCH] cxenstored: correct calculation of data/space in the
ring"):
> The cxenstored implementation can't handle cross ring boundary read and
> write. It gets aways with buggy behaviour because upper layer won't
> sleep when short-write or short-read occurs.
I don't understand w
The cxenstored implementation can't handle cross ring boundary read and
write. It gets aways with buggy behaviour because upper layer won't
sleep when short-write or short-read occurs.
It would be nice, however, to make the low level routine correct
regardless of what upper layer is doing. This sh
