From: Michael Buesch <mb@bu3sch.de>
To: "Tomas Winkler" <tomasw@gmail.com>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
"Ivo van Doorn" <ivdoorn@gmail.com>,
chris2553@googlemail.com, linux-wireless@vger.kernel.org
Subject: Re: Warning emited by 2.6.24-rc6-git5
Date: Tue, 8 Jan 2008 21:02:16 +0100 [thread overview]
Message-ID: <200801082102.16682.mb@bu3sch.de> (raw)
In-Reply-To: <1ba2fa240801081143y52e92c62o8ee2c3e701df7919@mail.gmail.com>
On Tuesday 08 January 2008 20:43:53 Tomas Winkler wrote:
> On Jan 8, 2008 7:22 PM, Johannes Berg <johannes@sipsolutions.net> wrote:
> >
> > On Tue, 2008-01-08 at 18:09 +0100, Johannes Berg wrote:
> > > > I didn't test the copy solution yet but in 11n rates I see as a show
> > > > stopper. All 11n packets are QoS packets.
> > >
> > > Really, go fix your firmware.
> >
>
> I don't think it is really broken. The packet it self is aligned. I'm
> not sure who has to be responsible for payload alignment you may have
> 10 other protocols packed into it, each with variable length
> unaligned header.
Yeah sure. You can move data around in the kernel and waste CPU,
or you can be clever and let the NIC firmware do it. Whatever you want
at intel. It's up to you. ;)
--
Greetings Michael.
next prev parent reply other threads:[~2008-01-08 20:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-29 9:42 Warning emited by 2.6.24-rc6-git5 Chris Clayton
2007-12-29 9:54 ` Johannes Berg
2007-12-29 10:21 ` Ivo van Doorn
2007-12-29 10:26 ` Johannes Berg
2007-12-29 10:36 ` Johannes Berg
2007-12-29 11:47 ` Ivo van Doorn
2007-12-29 11:59 ` Johannes Berg
2007-12-29 12:01 ` Johannes Berg
2007-12-29 14:29 ` Ivo van Doorn
2007-12-29 14:40 ` Johannes Berg
2007-12-29 15:14 ` Ivo van Doorn
2007-12-30 11:49 ` Chris Clayton
2007-12-30 12:11 ` Ivo van Doorn
2007-12-30 19:26 ` Chris Clayton
2007-12-30 22:01 ` Ivo van Doorn
2007-12-31 7:27 ` Kalle Valo
2007-12-31 7:56 ` Ivo Van Doorn
2008-01-02 6:32 ` Chris Clayton
2008-01-02 19:02 ` Ivo van Doorn
2008-01-04 17:09 ` Chris Clayton
2008-01-06 7:49 ` Andrew Price
2008-01-08 6:03 ` Chris Clayton
2008-01-02 8:11 ` Johannes Berg
2008-01-02 19:12 ` Ivo van Doorn
2008-01-08 15:44 ` Tomas Winkler
2008-01-08 17:09 ` Johannes Berg
2008-01-08 17:22 ` Johannes Berg
2008-01-08 19:43 ` Tomas Winkler
2008-01-08 20:02 ` Michael Buesch [this message]
2008-01-08 23:18 ` Tomas Winkler
2008-01-09 12:49 ` Johannes Berg
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=200801082102.16682.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=chris2553@googlemail.com \
--cc=ivdoorn@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=tomasw@gmail.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).