From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Gabor Juhos <juhosg@openwrt.org>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com
Subject: Re: [PATCH 1/2] rt2x00: convert rt2x00_ops.extra_tx_headroom to be a fuction
Date: Thu, 6 Jun 2013 14:36:03 +0200 [thread overview]
Message-ID: <20130606123602.GA3183@redhat.com> (raw)
In-Reply-To: <51AF9852.5020404@openwrt.org>
On Wed, Jun 05, 2013 at 09:58:10PM +0200, Gabor Juhos wrote:
> > Could we rather get rid of that extra_tx_headroom variable and use queue
> > parameters: winfo_size and desc_size ?
>
> Yes, it seems that we can compute the value of extra_tx_headrom from those
> fields. The driver uses the following values now:
>
> driver/device desc_size winfo_size extra_tx_headroom
>
> rt2400pci TXD_DESC_SIZE 0 0
> rt2500pci TXD_DESC_SIZE 0 0
> rt2800pci TXD_DESC_SIZE TXWI_DESC_SIZE TXWI_DESC_SIZE
> rt61pci TXD_DESC_SIZE 0 0
>
> rt2500usb TXD_DESC_SIZE 0 TXD_DESC_SIZE
> rt2800usb TXINFO_DESC_SIZE TXWI_DESC_SIZE TXINFO_DESC_SIZE +
> TXWI_DESC_SIZE
> rt2800usb/RT5592 TXINFO_DESC_SIZE TXWI_DESC_SIZE_5592 TXINFO_DESC_SIZE +
> TXWI_DESC_SIZE_5592
> rt73usb TXD_DESC_SIZE 0 TXD_DESC_SIZE
>
> On USB devices we can get it from desc_size + winfo_size and on PCI/PCIe/SoC
> devices it equals with winfo_size. So the callbacks and the extra_tx_headroom
> field in rt2x00_ops can be removed.
>
> However I would keep the new extra_tx_headroom field in rt2x00_dev. It would
> ensure that we don't have to compute its value every time it is used.
Ok, that make sense.
Thanks
Stanislaw
prev parent reply other threads:[~2013-06-06 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 10:53 [PATCH 1/2] rt2x00: convert rt2x00_ops.extra_tx_headroom to be a fuction Gabor Juhos
2013-06-05 10:54 ` [PATCH 2/2] rt2x00: rt2800usb: nuke rt2800usb_ops_5592 Gabor Juhos
2013-06-05 12:51 ` [PATCH 1/2] rt2x00: convert rt2x00_ops.extra_tx_headroom to be a fuction Stanislaw Gruszka
2013-06-05 19:58 ` Gabor Juhos
2013-06-06 12:36 ` Stanislaw Gruszka [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=20130606123602.GA3183@redhat.com \
--to=sgruszka@redhat.com \
--cc=juhosg@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=users@rt2x00.serialmonkey.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).