Re: [v2 PATCH 0/3] rhashtable: Handle table allocation failure during insertion

2017-02-13 Thread David Miller
From: Herbert Xu Date: Sat, 11 Feb 2017 19:24:22 +0800 > This series tackles the problem of table allocation failures during > insertion. The issue is that we cannot vmalloc during insertion. > This series deals with this by introducing nested tables. > > The first two patches removes manual ha

[v2 PATCH 0/3] rhashtable: Handle table allocation failure during insertion

2017-02-11 Thread Herbert Xu
Hi: v2 - Added Ack to patch 2. Fixed RCU annotation in code path executed by rehasher by using rht_dereference_bucket. v1 - This series tackles the problem of table allocation failures during insertion. The issue is that we cannot vmalloc during insertion. This series deals with this by introd

Re: [PATCH 0/3] rhashtable: Handle table allocation failure during insertion

2017-02-11 Thread Herbert Xu
On Wed, Feb 08, 2017 at 01:26:42PM -0500, David Miller wrote: > rhashtable is indeed getting quite complex, but I understand your > motivation for doing this work. > > I also agree that only true OOM situations should cause insertion > failures. > > Given the delicate nature of change rhashtable

Re: [PATCH 0/3] rhashtable: Handle table allocation failure during insertion

2017-02-08 Thread David Miller
From: Herbert Xu Date: Tue, 7 Feb 2017 20:38:27 +0800 > This series tackles the problem of table allocation failures during > insertion. The issue is that we cannot vmalloc during insertion. > This series deals with this by introducing nested tables. > > The first two patches removes manual has

[PATCH 0/3] rhashtable: Handle table allocation failure during insertion

2017-02-07 Thread Herbert Xu
Hi: This series tackles the problem of table allocation failures during insertion. The issue is that we cannot vmalloc during insertion. This series deals with this by introducing nested tables. The first two patches removes manual hash table walks which cannot work on a nested table. The final