[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180327190635-mutt-send-email-mst@kernel.org>
Date: Tue, 27 Mar 2018 19:07:22 +0300
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Michal Hocko <mhocko@...nel.org>
Cc: Wei Wang <wei.w.wang@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
virtio-dev@...ts.oasis-open.org, linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org, kvm@...r.kernel.org,
linux-mm@...ck.org, pbonzini@...hat.com,
liliang.opensource@...il.com, yang.zhang.wz@...il.com,
quan.xu0@...il.com, nilal@...hat.com, riel@...hat.com,
huangzhichao@...wei.com
Subject: Re: [PATCH v29 1/4] mm: support reporting free page blocks
On Tue, Mar 27, 2018 at 08:33:22AM +0200, Michal Hocko wrote:
> > > > + * The function itself might sleep so it cannot be called from atomic
> > > > + * contexts.
> > > I don't see how walk_free_mem_block() can sleep.
> >
> > OK, it would be better to remove this sentence for the current version. But
> > I think we could probably keep it if we decide to add cond_resched() below.
>
> The point of this sentence was to make any user aware that the function
> might sleep from the very begining rather than chase existing callers
> when we need to add cond_resched or sleep for any other reason. So I
> would rather keep it.
Let's say what it is then - "will be changed to sleep in the future".
> --
> Michal Hocko
> SUSE Labs
Powered by blists - more mailing lists