On Tue, Feb 01, 2011 at 04:20:16PM +, Daniel P. Berrange wrote:
> On Tue, Feb 01, 2011 at 09:18:45AM -0700, Eric Blake wrote:
> > On 02/01/2011 09:09 AM, Daniel P. Berrange wrote:
> > > In the SASL codepath we typically read far more data off the
> > > wire than we immediately need. When using
On Tue, Feb 01, 2011 at 09:18:45AM -0700, Eric Blake wrote:
> On 02/01/2011 09:09 AM, Daniel P. Berrange wrote:
> > In the SASL codepath we typically read far more data off the
> > wire than we immediately need. When using a connection from a
> > single thread this isn't a problem, since only our r
On 02/01/2011 09:09 AM, Daniel P. Berrange wrote:
> In the SASL codepath we typically read far more data off the
> wire than we immediately need. When using a connection from a
> single thread this isn't a problem, since only our reply will
> be pending (or an event we can handle directly). When us
In the SASL codepath we typically read far more data off the
wire than we immediately need. When using a connection from a
single thread this isn't a problem, since only our reply will
be pending (or an event we can handle directly). When using a
connection from multiple threads though, we may read
