YAMAMOTO Takashi wrote:
> > Sure ioflush do not directly free memory, but vnodes' dirty page use
> > memory, don't they? If ioflush stops working, is pageadaemon able to
> > pageout that kind of memory?
> pagedaemon flushes dirty pages by itself, yes.
So this is not a problem to get ioflush tra
hi,
> YAMAMOTO Takashi wrote:
>
>> as i told you a few times, ioflush is not a thread to free memory.
>> pagedaemon is.
>
> Sure ioflush do not directly free memory, but vnodes' dirty page use
> memory, don't they? If ioflush stops working, is pageadaemon able to
> pageout that kind of memory?
YAMAMOTO Takashi wrote:
> as i told you a few times, ioflush is not a thread to free memory.
> pagedaemon is.
Sure ioflush do not directly free memory, but vnodes' dirty page use
memory, don't they? If ioflush stops working, is pageadaemon able to
pageout that kind of memory?
> please read ufs
In article <20110923163839.ga4...@kleink.org>,
Klaus Klein wrote:
>[Yay, catching up with a month's worth of source-changes...]
>
>On Mon, Aug 22, 2011 at 12:46:21PM +, Christos Zoulas wrote:
>> In article <20110822104822.gb15...@britannica.bec.de>,
>> Joerg Sonnenberger wrote:
>> >On Mon,
On Wed, Sep 14, 2011 at 08:32:44AM +0100, David Laight wrote:
> On Tue, Sep 13, 2011 at 03:07:44PM -0400, Christos Zoulas wrote:
> > Module Name:src
> > Committed By: christos
> > Date: Tue Sep 13 19:07:44 UTC 2011
> >
> > Modified Files:
> > src/external/bsd/bind/d
[Yay, catching up with a month's worth of source-changes...]
On Mon, Aug 22, 2011 at 12:46:21PM +, Christos Zoulas wrote:
> In article <20110822104822.gb15...@britannica.bec.de>,
> Joerg Sonnenberger wrote:
> >On Mon, Aug 22, 2011 at 01:26:24AM +, David Holland wrote:
> >> On Mon, Aug 22
hi,
> YAMAMOTO Takashi wrote:
>
>> > This avoids deadlocks in the following situations:
>> > 1) when memory is low: ioflush waits the fileystem, the fielsystem waits
>> >for memory
>> can you explain how it is a problem?
>
> As I understand, one way to free memory is to flush vnode backed
On Fri, Sep 23, 2011 at 05:09:23AM +, YAMAMOTO Takashi wrote:
> > Fix the build that was broken by struct lwp *updateproc reference in
> > RUMP-visible code. Instead of checking that updateproc (aka ioflush,
> > aka syncer) will not sleep in PUFFS code, I check for any kernel thread:
> > after
