[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130327.131006.2142647165754132919.davem@davemloft.net>
Date: Wed, 27 Mar 2013 13:10:06 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: eric.dumazet@...il.com
Cc: brouer@...hat.com, netdev@...r.kernel.org, fw@...len.de,
dborkman@...hat.com, hannes@...essinduktion.org
Subject: Re: [net-next PATCH 1/3] net: frag, avoid several CPUs grabbing
same frag queue during LRU evictor loop
From: Eric Dumazet <eric.dumazet@...il.com>
Date: Wed, 27 Mar 2013 09:14:04 -0700
> On Wed, 2013-03-27 at 16:55 +0100, Jesper Dangaard Brouer wrote:
>> The LRU list is protected by its own lock, since commit 3ef0eb0db4
>> (net: frag, move LRU list maintenance outside of rwlock), and
>> no-longer by a read_lock.
>>
>> This makes it possible, to remove the inet_frag_queue, which is about
>> to be "evicted", from the LRU list head. This avoids the problem, of
>> several CPUs grabbing the same frag queue.
>>
>> Note, cannot remove the inet_frag_lru_del() call in fq_unlink()
>> called by inet_frag_kill(), because inet_frag_kill() is also used in
>> other situations. Thus, we use list_del_init() to allow this
>> double list_del to work.
>>
>> Signed-off-by: Jesper Dangaard Brouer <brouer@...hat.com>
>> ---
>>
>> net/ipv4/inet_fragment.c | 3 +++
>> 1 files changed, 3 insertions(+), 0 deletions(-)
>>
>
> Acked-by: Eric Dumazet <edumazet@...gle.com>
Applied.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists