netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lennert Buytenhek <buytenh@wantstofly.org>
To: Philip Rakity <prakity@marvell.com>
Cc: Sachin Sanap <ssanap@marvell.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Ashish Karkare <akarkare@marvell.com>,
	Prabhanjan Sarnaik <sarnaik@marvell.com>,
	"eric.y.miao@gmail.com" <eric.y.miao@gmail.com>,
	Mark Brown <markb@marvell.com>
Subject: Re: [PATCH v2]  net: add Fast Ethernet driver for PXA168.
Date: Tue, 10 Aug 2010 20:01:54 +0200	[thread overview]
Message-ID: <20100810180154.GD25474@mail.wantstofly.org> (raw)
In-Reply-To: <6546F80B-0B5E-4F41-A500-7B75493A42DE@marvell.com>

On Tue, Aug 10, 2010 at 10:55:02AM -0700, Philip Rakity wrote:

> We agree that extra header prepend space is needed.  The solution of
> globally defining SKB_NET_PAD to increase this area for all drivers
> is where I have some concern.  The solution certainly works but at
> the cost of extra space for drivers that do not need to do this.
> The solution is fine by me and maybe the best answer is to increase
> the value in the standard linux implementation from 32 to 48 or 64 bytes. 

What I said was:

| This seems like something that, should you want to handle it, should be
| handled centrally (e.g. by conditionally increasing NET_SKB_PAD or so)
| and not hardcoded into one specific driver only.

In other words, "don't hardcode it into your driver just because you
think that most users will want to use your driver for bridging/routing
to wlan".

It makes no sense to categorically declare that "pxa168_eth will always
be used for routing to wireless, so we'll add some extra headroom by
default there, but e1000e will not, so there we won't".

Even if this stays a private kernel tree hack, I would still do it
globally rather than locally.


> > > 11n needs more.
> > 
> > Really?  Pointer?

Still curious about this.

  reply	other threads:[~2010-08-10 18:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-04 10:47 [PATCH] net: add Fast Ethernet driver for PXA168 Sachin Sanap
2010-08-04  6:58 ` Lennert Buytenhek
2010-08-04  7:08   ` Eric Miao
2010-08-04  7:09     ` Eric Miao
2010-08-04  7:17     ` Lennert Buytenhek
2010-08-04  7:56   ` Simon Horman
2010-08-06 15:14   ` Sachin Sanap
2010-08-06 15:44     ` Philip Rakity
2010-08-06 16:55       ` Sachin Sanap
2010-08-06 17:02         ` Joe Perches
2010-08-10 11:40       ` Lennert Buytenhek
2010-08-06 18:02     ` Philip Rakity
2010-08-10  8:30       ` [PATCH v2] " Sachin Sanap
2010-08-10 12:33         ` Lennert Buytenhek
2010-08-10 16:24           ` Philip Rakity
2010-08-10 17:30             ` Lennert Buytenhek
2010-08-10 17:55               ` Philip Rakity
2010-08-10 18:01                 ` Lennert Buytenhek [this message]
2010-08-10 18:12                   ` Philip Rakity
2010-08-10 23:42                     ` David Miller
2010-08-14  7:08           ` Sachin Sanap
2010-08-14  7:22           ` [PATCH v3] " Sachin Sanap
2010-08-14 20:47             ` Philip Rakity
2010-08-16 10:07               ` Sachin Sanap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100810180154.GD25474@mail.wantstofly.org \
    --to=buytenh@wantstofly.org \
    --cc=akarkare@marvell.com \
    --cc=eric.y.miao@gmail.com \
    --cc=markb@marvell.com \
    --cc=netdev@vger.kernel.org \
    --cc=prakity@marvell.com \
    --cc=sarnaik@marvell.com \
    --cc=ssanap@marvell.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).