Re: [Patch 4/5] Network Drop Monitor: Adding drop monitor implementation & Netlink protocol

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Evgeniy Polyakov
Date: Tuesday, March 3, 2009 - 11:19 am

Hi Neil.

On Tue, Mar 03, 2009 at 12:04:35PM -0500, Neil Horman (nhorman@tuxdriver.com) wrote:

Ugh, please add either some comments about its alignment or some padding
fields.


Isn't size_t have different size on different platforms?


Static dm data?


DEFINE_SPINLOCK


Configurable?


Should it be plain get_cpu_var() or disabled preemption?


Hmm, this worries a bit, shouldn't it use NLMSG_LENGTH() and friends?


Additional space                    sneaked in.


Another 3. Also why do you use zero allocation instead of GFP_ATOMIC?
Also why do you use global lock here?


Trailing tab and unneded new line.


Please add some comments that it is called from the timer interrupt and
thus should not disable preemption around per-cpu variable.


Looks like a netlink message to/from userspace contains pointer. If this
is the case, then it is not the way to go.


What if there is no space?


Please change the structures so that they never contain variable size
members like pointers or longs.




Additional newline.


And another one.


Why? :)


Please use NLMSG helpers here.


-- 
	Evgeniy Polyakov
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [Patch 4/5] Network Drop Monitor: Adding drop monitor ..., Evgeniy Polyakov, (Tue Mar 3, 11:19 am)