Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Ron Rindjunsky <ron.rindjunsky@intel.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: iwlwifi and tx info in skb->cb
Date: Fri, 09 May 2008 00:10:56 +0200	[thread overview]
Message-ID: <1210284656.3547.76.camel@johannes.berg> (raw)
In-Reply-To: <1ba2fa240805081507j7cf991ffo5bae443b0b77a39e@mail.gmail.com> (sfid-20080509_000624_162294_5A80849B)

[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]


> >  > Currently we actively use 2 of them. First for TX command second for
> >  > actual frame.  It would be even worth if we need to expand
> >  > each packet also for TX command.
> >
> >  We will no longer do that after davem and I figure out those allocation
> >  patches.
> 
> Not sure these things are connected. TX command is allocated fixed for each TFD.

Ah, no, I misread that. Well, I think it might still help to say you
need N bytes headroom and use those since you wouldn't have to allocate
an extra skb.

> >  You should implement TCP checksumming in the hardware. *that* would help
> >  a lot.
> 
> There is already pretty much deal of link layer in software to reduce
> the cost and the complexity of the HW for these softmac NICs so
> this would be kind of strange investment...but I didn't invest much
> thoughts into yet.
> There are probably other means to utilize scatter gather DMA then TCP
> off loading. Are they any other source of scattered packets maybe
> iovec?

Well as far as I know those too would be zero-copy IO which only works
if you have TCP checksumming in hardware.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2008-05-08 22:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07 22:01 iwlwifi and tx info in skb->cb Johannes Berg
2008-05-07 23:29 ` Tomas Winkler
2008-05-07 23:30   ` Johannes Berg
2008-05-08  0:21     ` Tomas Winkler
2008-05-08 14:05       ` Johannes Berg
2008-05-08 22:07         ` Tomas Winkler
2008-05-08 22:10           ` Johannes Berg [this message]
2008-05-08 22:28             ` Tomas Winkler
2008-05-08 22:30               ` Johannes Berg
2008-05-08 23:16                 ` Tomas Winkler
2008-05-08 23:17                   ` Johannes Berg
2008-05-08 23:20                     ` Johannes Berg
2008-05-08 23:20                   ` David Miller
2008-05-08 23:30                     ` Tomas Winkler

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=1210284656.3547.76.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=ron.rindjunsky@intel.com \
    --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