All of lore.kernel.org
 help / color / mirror / Atom feed
From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: linux-wireless@vger.kernel.org
Cc: Dan Williams <dcbw@redhat.com>, libertas-dev@lists.infradead.org
Subject: Re: [PATCH] libertas: fix spinlock recursion bug
Date: Thu, 27 Mar 2008 09:17:46 +0100	[thread overview]
Message-ID: <200803270917.46334.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <1206552791.31383.99.camel@localhost.localdomain>

Hi Dan !

I like most of your proposition. A few things:


> struct lbs_event {
> 	u32 event;  /* MACREG_INT_CODE_xxxxx */
> 	u32 len;
> 	u8 buf[LBS_UPLD_SIZE];
> };

Ugh, as LBS_UPLD_SIZE equals to to 2312, this looks ugly. I'm not 
sure if accessing the cmd_ctrl_node list directly would be a 
good idea, thought.


> Seems better than what's there.

Definitely. Maybe David Woodhouse can give his opinion as well.


> I might take a stab at this if people think it seems sane
> enough.

Do you have time for such a thing?  I see that you don't ack some 
of my patches, probably because you don't even have time to 
check them. What time frame do you have in mind?


> The memory hit over what's there now would be ~15K of allocated
> memory at driver load per card.

The memory hit won't be nice for embedded devices. But maybe it's 
better to try this solution first, to see if it's working. Then 
we have all the time for optimizations, e.g. with two lists.

  reply	other threads:[~2008-03-27  8:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-19 14:24 [PATCH] libertas: fix spinlock recursion bug Holger Schurig
2008-03-19 15:02 ` Dan Williams
2008-03-26  7:48   ` Holger Schurig
2008-03-26 14:41 ` Holger Schurig
2008-03-26 15:17   ` Dan Williams
2008-03-26 15:37     ` Holger Schurig
2008-03-26 17:33       ` Dan Williams
2008-03-27  8:17         ` Holger Schurig [this message]
2008-03-27 10:08         ` Holger Schurig
2008-03-27 11:34           ` Dan Williams
2008-03-27 11:57             ` Holger Schurig
2008-03-27 14:31               ` Dan Williams

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=200803270917.46334.hs4233@mail.mn-solutions.de \
    --to=hs4233@mail.mn-solutions.de \
    --cc=dcbw@redhat.com \
    --cc=libertas-dev@lists.infradead.org \
    --cc=linux-wireless@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 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.