linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Wey-Yi Guy <wey-yi.w.guy@intel.com>,
	Intel Linux Wireless <ilw@linux.intel.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] iwlwifi: zero fill txq->txb on queue reset
Date: Tue, 15 Feb 2011 14:06:22 +0100	[thread overview]
Message-ID: <20110215130621.GB2515@redhat.com> (raw)
In-Reply-To: <1297770482.3935.1.camel@jlt3.sipsolutions.net>

On Tue, Feb 15, 2011 at 12:48:02PM +0100, Johannes Berg wrote:
> On Tue, 2011-02-15 at 12:39 +0100, Stanislaw Gruszka wrote:
> 
> > > > >  	if (txq_id == priv->cmd_queue)
> > > > >  		actual_slots++;
> > > > > +	else
> > > > > +		memset(txq->txb, 0, sizeof(txq->txb[0]) * TFD_QUEUE_SIZE_MAX);
> > > > 
> > > > I don't mind -- but I think the changelog should say that this isn't
> > > > necessary since the device will never use any of those entries?
> > > 
> > > Err, I confused txb and tfds. But it still shouldn't be necessary --
> > > aren't the entries reset to NULL when taken out of use?
> > 
> > There are memset zero before the use in {iwlagn,iwl3945}_tx_skb(),
> > so patch is unneeded as well kzalloc in current code (I add replace
> > to kmalloc to my todo list).
> 
> Well, don't worry, the change is fine -- 

hmm, I think is not, it just add more confusion

Stanislaw

      reply	other threads:[~2011-02-15 13:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14 14:33 [PATCH] iwlwifi: zero fill txq->txb on queue reset Stanislaw Gruszka
2011-02-14 14:53 ` Johannes Berg
2011-02-14 14:55   ` Johannes Berg
2011-02-15 11:39     ` Stanislaw Gruszka
2011-02-15 11:48       ` Johannes Berg
2011-02-15 13:06         ` 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=20110215130621.GB2515@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=ilw@linux.intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wey-yi.w.guy@intel.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).