[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1353937351.11754.207.camel@localhost>
Date: Mon, 26 Nov 2012 14:42:31 +0100
From: Jesper Dangaard Brouer <jbrouer@...hat.com>
To: Cong Wang <amwang@...hat.com>, David Miller <davem@...hat.com>
Cc: netdev@...r.kernel.org, Eric Dumazet <eric.dumazet@...il.com>
Subject: Re: [PATCH net-next v2] net: clean up locking in inet_frag_find()
Could we please hold back on this cleanup patch, as I have a stack of 9
patches modifying this area.
If people find this cleanup useful/correct?, I can integrate it into my
patch stack...
--Jesper
On Mon, 2012-11-26 at 15:26 +0800, Cong Wang wrote:
> It is weird to take the read lock outside of inet_frag_find()
> but release it inside... This can be improved by refactoring
> the code, that is, introducing inet{4,6}_frag_find() which call
> the their own hash function, inet{4,6}_hash_frag(), hiding the
> details from their callers.
--
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