From: Joe Perches <joe@perches.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] mac80211: add TX fastpath
Date: Mon, 30 Mar 2015 09:42:47 -0700 [thread overview]
Message-ID: <1427733767.14276.13.camel@perches.com> (raw)
In-Reply-To: <1427728036.26117.36.camel@sipsolutions.net>
On Mon, 2015-03-30 at 17:07 +0200, Johannes Berg wrote:
> On Mon, 2015-03-30 at 08:03 -0700, Joe Perches wrote:
>
> > > diff --git a/net/mac80211/tx.c b/net/mac80211/tx.c
> > []
> > > +void ieee80211_check_fast_xmit(struct sta_info *sta, gfp_t gfp)
> > > +{
> > > + struct ieee80211_fast_tx build = {}, *fast_tx, *old;
> >
> > This "{}" memset should probably be moved farther down
> > because there are many return paths that are possible
> > before the memset is necessary.
>
> True. However, this isn't actually the fast path I'm interested in; the
> function ieee80211_xmit_fast() is the one that we execute per packet,
> this one is invoked very infrequently. I prefer the more readable way
> here.
Perhaps using {} as an initializer amidst multiple declarations
on the same line isn't particularly readable and the explicit
memset is better.
prev parent reply other threads:[~2015-03-30 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 14:36 [PATCH 1/2] mac80211: add TX fastpath Johannes Berg
2015-03-30 14:36 ` [PATCH 2/2] mac80211_hwsim: enable fast-xmit Johannes Berg
2015-03-30 14:49 ` [PATCH 1/2] mac80211: add TX fastpath Johannes Berg
2015-03-30 15:03 ` Joe Perches
2015-03-30 15:07 ` Johannes Berg
2015-03-30 16:42 ` Joe Perches [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=1427733767.14276.13.camel@perches.com \
--to=joe@perches.com \
--cc=johannes@sipsolutions.net \
--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.