Re: [PATCH 1/4] net: VM deadlock avoidance framework

2006-08-29 Thread Indan Zupancic
On Tue, August 29, 2006 11:49, Peter Zijlstra said: > On Tue, 2006-08-29 at 02:01 +0200, Indan Zupancic wrote: >> Good that you're aware of it. Thing is, how much sense does the split-up into >> adjust_memalloc_reserve() and sk_adjust_memalloc() make at this point? Why >> not >> merge the code of

Re: [PATCH 1/4] net: VM deadlock avoidance framework

2006-08-29 Thread Peter Zijlstra
On Tue, 2006-08-29 at 02:01 +0200, Indan Zupancic wrote: > On Mon, August 28, 2006 19:32, Peter Zijlstra said: > > Ah, no accident there, I'm fully aware that there would need to be a > > spinlock in adjust_memalloc_reserve() if there were another caller. > > (I even had it there for some time) -

Re: [PATCH 1/4] net: VM deadlock avoidance framework

2006-08-28 Thread Indan Zupancic
On Mon, August 28, 2006 19:32, Peter Zijlstra said: > Also, I'm really past caring what the thing > is called ;-) But if ppl object I guess its easy enough to run yet > another sed command over the patches. True, same here. >> >> You can get rid of the memalloc_reserve and vmio_request_queues var

Re: [PATCH 1/4] net: VM deadlock avoidance framework

2006-08-28 Thread Peter Zijlstra
On Mon, 2006-08-28 at 18:03 +0200, Indan Zupancic wrote: > On Mon, August 28, 2006 12:22, Peter Zijlstra said: > >> > @@ -391,6 +391,7 @@ enum sock_flags { > >> > SOCK_RCVTSTAMP, /* %SO_TIMESTAMP setting */ > >> > SOCK_LOCALROUTE, /* route locally only, %SO_DONTROUTE setting */ >

Re: [PATCH 1/4] net: VM deadlock avoidance framework

2006-08-28 Thread Indan Zupancic
On Mon, August 28, 2006 12:22, Peter Zijlstra said: > On Sat, 2006-08-26 at 04:37 +0200, Indan Zupancic wrote: >> Why not 'emergency'? Looks like 'emerge' with a typo now. ;-) > > hehe, me lazy, you gentoo ;-) > sed -i -e 's/emerg/emregency/g' -e 's/EMERG/EMERGENCY/g' *.patch I used it for a while

Re: [PATCH 1/4] net: VM deadlock avoidance framework

2006-08-28 Thread Peter Zijlstra
On Sat, 2006-08-26 at 04:37 +0200, Indan Zupancic wrote: > On Fri, August 25, 2006 17:39, Peter Zijlstra said: > > @@ -282,7 +282,8 @@ struct sk_buff { > > nfctinfo:3; > > __u8pkt_type:3, > > fclone:2, > > -

Re: [PATCH 1/4] net: VM deadlock avoidance framework

2006-08-25 Thread Indan Zupancic
On Fri, August 25, 2006 17:39, Peter Zijlstra said: > @@ -282,7 +282,8 @@ struct sk_buff { > nfctinfo:3; > __u8pkt_type:3, > fclone:2, > - ipvs_property:1; > +

[PATCH 1/4] net: VM deadlock avoidance framework

2006-08-25 Thread Peter Zijlstra
The core of the VM deadlock avoidance framework. In order to provide robust networked block devices there must be a guarantee of progress. That is, the block device must never stall because of OOM because the device itself might be needed to get out of OOM (reclaim pageout). This means that the