* Network device with variable hard header len
@ 2009-01-10 11:28 Dmitry Eremin-Solenikov
2009-01-12 11:48 ` Mark Brown
0 siblings, 1 reply; 2+ messages in thread
From: Dmitry Eremin-Solenikov @ 2009-01-10 11:28 UTC (permalink / raw)
To: linux-kernel
Hi,
Sorry if this a dumb question. Currently I'm programming a driver for
the devices with variable network header len. From the Linux net stack
perspective what should I do: set netdev->hard_header_len to maximum
possible header and use less space that specified there or set
netdev->needed_headroom to that value?
If that metters, I'll be implementing my own set of header_ops in any
case.
Thank you
--
With best wishes
Dmitry
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Network device with variable hard header len
2009-01-10 11:28 Network device with variable hard header len Dmitry Eremin-Solenikov
@ 2009-01-12 11:48 ` Mark Brown
0 siblings, 0 replies; 2+ messages in thread
From: Mark Brown @ 2009-01-12 11:48 UTC (permalink / raw)
To: Dmitry Eremin-Solenikov; +Cc: linux-kernel, netdev
On Sat, Jan 10, 2009 at 02:28:12PM +0300, Dmitry Eremin-Solenikov wrote:
> Sorry if this a dumb question. Currently I'm programming a driver for
> the devices with variable network header len. From the Linux net stack
> perspective what should I do: set netdev->hard_header_len to maximum
> possible header and use less space that specified there or set
> netdev->needed_headroom to that value?
> If that metters, I'll be implementing my own set of header_ops in any
> case.
This is probably better asked on netdev (CCed).
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-01-12 12:07 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-01-10 11:28 Network device with variable hard header len Dmitry Eremin-Solenikov
2009-01-12 11:48 ` Mark Brown
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).