public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jouni Malinen <jkmaline@cc.hut.fi>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: PATCH: Better fixup for the orinoco driver
Date: Sat, 15 Oct 2005 19:11:10 -0700	[thread overview]
Message-ID: <20051016021110.GC10699@jm.kir.nu> (raw)
In-Reply-To: <1129401680.17923.3.camel@localhost.localdomain>

On Sat, Oct 15, 2005 at 07:41:20PM +0100, Alan Cox wrote:

> The latest kernel added a pretty ugly fix for the orinoco etherleak bug
> which contains bogus skb->len checks already done by the caller and
> causes copies of all odd sized frames (which are quite common)
> 
> While the skb->len check should be ripped out the other fix is harder to
> do properly so I'm proposing for this the -mm tree only until next 2.6.x
> so that it gets tested.
> 
> Instead of copying buffers around blindly this code implements a padding
> aware version of the hermes buffer writing function which does padding
> as the buffer is loaded and thus more cleanly and without bogus 1.5K
> copies.

While working on this area, shouldn't we just finally get rid of the
bogus ETH_ZLEN padding? There is no such requirement for IEEE 802.11.
This would remove need for the extra padding code you have in
hermes_bap_pwrite_pad(). The only requirement is to be able to add one
extra byte if the packet length is odd.

-- 
Jouni Malinen                                            PGP id EFC895FA

      reply	other threads:[~2005-10-16  2:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-15 18:41 PATCH: Better fixup for the orinoco driver Alan Cox
2005-10-16  2:11 ` Jouni Malinen [this message]

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=20051016021110.GC10699@jm.kir.nu \
    --to=jkmaline@cc.hut.fi \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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