* Josef Bacik wrote:
> On Fri, Sep 20, 2013 at 07:12:47AM +0200, Ingo Molnar wrote:
> >
> > * Josef Bacik wrote:
> >
> > > We can starve out the transaction commit with a bunch of caching threads
> > > all running at the same time. This is because we will only drop the
> > > extent_commit_
On Fri, Sep 20, 2013 at 07:12:47AM +0200, Ingo Molnar wrote:
>
> * Josef Bacik wrote:
>
> > We can starve out the transaction commit with a bunch of caching threads
> > all running at the same time. This is because we will only drop the
> > extent_commit_sem if we need_resched(), which isn't
* Josef Bacik wrote:
> We can starve out the transaction commit with a bunch of caching threads
> all running at the same time. This is because we will only drop the
> extent_commit_sem if we need_resched(), which isn't likely to happen
> since we will be reading a lot from the disk so have
We can starve out the transaction commit with a bunch of caching threads all
running at the same time. This is because we will only drop the
extent_commit_sem if we need_resched(), which isn't likely to happen since we
will be reading a lot from the disk so have already schedule()'ed plenty. Alex
