2015-12-08 11:12, Yuanhan Liu:
> On Tue, Dec 08, 2015 at 03:30:43AM +0100, Thomas Monjalon wrote:
> > 2015-12-08 10:23, Yuanhan Liu:
> > > On Mon, Dec 07, 2015 at 04:50:21PM -0800, Stephen Hemminger wrote:
> > > > When guest is booting (or any othertime guest is busy) it is possible
> > > > for the
On Tue, Dec 08, 2015 at 03:30:43AM +0100, Thomas Monjalon wrote:
> 2015-12-08 10:23, Yuanhan Liu:
> > On Mon, Dec 07, 2015 at 04:50:21PM -0800, Stephen Hemminger wrote:
> > > When guest is booting (or any othertime guest is busy) it is possible
> > > for the small receive ring (256) to get full. If
On Mon, Dec 07, 2015 at 04:50:21PM -0800, Stephen Hemminger wrote:
> When guest is booting (or any othertime guest is busy) it is possible
> for the small receive ring (256) to get full. If this happens the
> vhost library should just return normally. It's current behavior
> of logging just creates
2015-12-08 10:23, Yuanhan Liu:
> On Mon, Dec 07, 2015 at 04:50:21PM -0800, Stephen Hemminger wrote:
> > When guest is booting (or any othertime guest is busy) it is possible
> > for the small receive ring (256) to get full. If this happens the
> > vhost library should just return normally. It's cur
When guest is booting (or any othertime guest is busy) it is possible
for the small receive ring (256) to get full. If this happens the
vhost library should just return normally. It's current behavior
of logging just creates massive log spew/overflow which could even
act as a DoS attack against hos
5 matches
Mail list logo
