Re: [RFC][PATCH 1/3] Introduce the net_device_ops structure.

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <kaber@...>
Cc: <shemminger@...>, <xemul@...>, <netdev@...>
Date: Monday, April 14, 2008 - 12:20 am

From: Patrick McHardy <kaber@trash.net>
Date: Fri, 04 Apr 2008 17:54:55 +0200


I echo the sentiments of Stephen (use const as much as possible)
and Patrick here.

In particular what Patrick is mentioning deserves special emphasis.

There are so many weird cases that take an existing device and then
overload one of the method pointers arbitrarily.  And I know this is
not at all limited to hard_start_xmit and hard_header.

It may therefore be very difficult to get things all the way over to
nd_ops except for a very small number pointers.  And unfortunately, if
this cannot be overcome, it limits the usefullness of the change. :-/

I encourage this work, nonetheless.
--
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:
[RFC][PATCH 1/3] Introduce the net_device_ops structure., Pavel Emelyanov, (Fri Apr 4, 10:10 am)
Re: [RFC][PATCH 1/3] Introduce the net_device_ops structure., Stephen Hemminger, (Fri Apr 4, 11:14 am)
Re: [RFC][PATCH 1/3] Introduce the net_device_ops structure., Patrick McHardy, (Fri Apr 4, 11:54 am)
Re: [RFC][PATCH 1/3] Introduce the net_device_ops structure., David Miller, (Mon Apr 14, 12:20 am)