All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Intel Linux Wireless <ilw@linux.intel.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH -iwlwifi] iwlwifi: make tx_cmd_pool kmem cache global
Date: Mon, 27 Feb 2012 06:30:16 -0800	[thread overview]
Message-ID: <1330353016.12612.13.camel@wwguy-huron> (raw)
In-Reply-To: <1330350725-5815-1-git-send-email-sgruszka@redhat.com>

Hi Stanislaw,

On Mon, 2012-02-27 at 14:52 +0100, Stanislaw Gruszka wrote:
> Otherwise we are not able to run more than one device per driver:
> 
> [   24.743045] kmem_cache_create: duplicate cache iwl_dev_cmd
> [   24.743051] Pid: 3165, comm: NetworkManager Not tainted 3.3.0-rc2-wl+ #5
> [   24.743054] Call Trace:
> [   24.743066]  [<ffffffff811717d5>] kmem_cache_create+0x655/0x700
> [   24.743073]  [<ffffffff81061415>] ? destroy_timer_on_stack+0x15/0x20
> [   24.743079]  [<ffffffff814e26ed>] ? schedule_timeout+0x1dd/0x330
> [   24.743083]  [<ffffffff810617c0>] ? lock_timer_base+0x70/0x70
> [   24.743101]  [<ffffffffa03b9f8b>] iwl_alive_notify+0x1cb/0x1f0 [iwlwifi]
> [   24.743111]  [<ffffffffa03ba442>] iwl_load_ucode_wait_alive+0x1b2/0x220 [iwlwifi]
> [   24.743118]  [<ffffffff810b1fbd>] ? trace_hardirqs_on+0xd/0x10
> [   24.743127]  [<ffffffffa03b9700>] ? iwlagn_mac_setup_register+0x2e0/0x2e0 [iwlwifi]
> [   24.743133]  [<ffffffff814e60b4>] ? _raw_spin_unlock_bh+0x34/0x40
> [   24.743142]  [<ffffffffa03ba893>] iwl_run_init_ucode+0x73/0x100 [iwlwifi]
> [   24.743152]  [<ffffffffa03b8fa1>] __iwl_up+0x81/0x220 [iwlwifi]
> [   24.743161]  [<ffffffffa03b91c0>] iwlagn_mac_start+0x80/0x190 [iwlwifi]
> [   24.743188]  [<ffffffffa03307b3>] ieee80211_do_open+0x293/0x770 [mac80211]
> 
> Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
> ---
> I tested patch on wireless testing tree, and then rebased to -iwlwifi
> tree, where did compile check only. This is basically a bugfix, but
> seems nobody except me (*) use more than one iwlwifi device per system,
> so I do not cc stable. 
> 

I am not totally understand what your patch doing, you make a global
iwl_tx_cmd_pool structure, how that fix the multiple devices problem?
global variable is not really a good programming exercise, true?

> (*) I wonder why Intel developers do not run many devices in their
> systems. I think they should - one new device and a few older. Then
> perhaps we will stop seeing so many breakage on older devices caused
> by adding support for new hardware and features.
> 

Yes, I am totally agree and we will start doing that

btw, thanks for the help, I will merge all the patches from you on our
internal tree first.

Thanks
Wey




  reply	other threads:[~2012-02-27 15:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27 13:52 [PATCH -iwlwifi] iwlwifi: make tx_cmd_pool kmem cache global Stanislaw Gruszka
2012-02-27 14:30 ` Guy, Wey-Yi [this message]
2012-02-27 17:55   ` Emmanuel Grumbach
2012-02-27 17:48     ` Guy, Wey-Yi
2012-02-27 20:20       ` Emmanuel Grumbach
2012-02-27 22:14         ` Guy, Wey-Yi
2012-02-29  9:00 ` Johannes Berg
2012-02-29 15:00   ` Guy, Wey-Yi

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=1330353016.12612.13.camel@wwguy-huron \
    --to=wey-yi.w.guy@intel.com \
    --cc=ilw@linux.intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sgruszka@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.