Return-path: Received: from smtp.rutgers.edu ([128.6.72.243]:17597 "EHLO annwn13.rutgers.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1946105AbXBIFMh (ORCPT ); Fri, 9 Feb 2007 00:12:37 -0500 From: Michael Wu To: Jiri Benc Subject: [PATCH] d80211: remove hosttime from ieee80211_rx_status Date: Thu, 8 Feb 2007 23:59:42 -0500 Cc: linux-wireless@vger.kernel.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2647275.Geb85LW4o3"; protocol="application/pgp-signature"; micalg=pgp-sha1 Message-Id: <200702082359.47085.flamingice@sourmilk.net> Sender: linux-wireless-owner@vger.kernel.org List-ID: --nextPart2647275.Geb85LW4o3 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline d80211: remove hosttime from ieee80211_rx_status Nobody fills hosttime in ieee80211_rx_status. Removing it allows ieee80211_rx_status to fit in skb->cb. Signed-off-by: Michael Wu =2D-- include/net/d80211.h | 1 - net/d80211/ieee80211.c | 25 +++++-------------------- 2 files changed, 5 insertions(+), 21 deletions(-) diff --git a/include/net/d80211.h b/include/net/d80211.h index 326def5..0b7b963 100644 =2D-- a/include/net/d80211.h +++ b/include/net/d80211.h @@ -225,7 +225,6 @@ struct ieee80211_tx_control { * (the subset supported by hardware) to the 802.11 code with each received * frame. */ struct ieee80211_rx_status { =2D u64 hosttime; u64 mactime; int freq; /* receive frequency in Mhz */ int channel; diff --git a/net/d80211/ieee80211.c b/net/d80211/ieee80211.c index bbcefa9..7a92bfe 100644 =2D-- a/net/d80211/ieee80211.c +++ b/net/d80211/ieee80211.c @@ -2627,7 +2627,7 @@ ieee80211_fill_frame_info(struct ieee802 struct timespec ts; struct ieee80211_rate *rate; =20 =2D jiffies_to_timespec(status->hosttime, &ts); + jiffies_to_timespec(jiffies, &ts); fi->hosttime =3D cpu_to_be64((u64) ts.tv_sec * 1000000 + ts.tv_nsec / 1000); fi->mactime =3D cpu_to_be64(status->mactime); @@ -4019,25 +4019,11 @@ static void ieee80211_stat_refresh(unsig void ieee80211_rx_irqsafe(struct ieee80211_hw *hw, struct sk_buff *skb, struct ieee80211_rx_status *status) { =2D struct ieee80211_rx_status *saved; struct ieee80211_local *local =3D hw_to_local(hw); =20 skb->dev =3D local->mdev; =2D saved =3D kmalloc(sizeof(struct ieee80211_rx_status), GFP_ATOMIC); =2D if (unlikely(!saved)) { =2D if (net_ratelimit()) =2D printk(KERN_WARNING "%s: Not enough memory, " =2D "dropping packet", skb->dev->name); =2D /* should be dev_kfree_skb_irq, but due to this function being =2D * named _irqsafe instead of just _irq we can't be sure that =2D * people won't call it from non-irq contexts */ =2D dev_kfree_skb_any(skb); =2D return; =2D } =2D memcpy(saved, status, sizeof(struct ieee80211_rx_status)); =2D /* copy pointer to saved status into skb->cb for use by tasklet */ =2D memcpy(skb->cb, &saved, sizeof(saved)); =2D + /* copy status into skb->cb for use by tasklet */ + memcpy(skb->cb, status, sizeof(struct ieee80211_rx_status)); skb->pkt_type =3D ieee80211_rx_msg; skb_queue_tail(&local->skb_queue, skb); tasklet_schedule(&local->tasklet); @@ -4096,13 +4082,12 @@ static void ieee80211_tasklet_handler(un (skb =3D skb_dequeue(&local->skb_queue_unreliable))) { switch (skb->pkt_type) { case ieee80211_rx_msg: =2D /* get pointer to saved status out of skb->cb */ =2D memcpy(&rx_status, skb->cb, sizeof(rx_status)); + /* status is in skb->cb */ + rx_status =3D (struct ieee80211_rx_status *) skb->cb; /* Clear skb->type in order to not confuse kernel * netstack. */ skb->pkt_type =3D 0; __ieee80211_rx(local_to_hw(local), skb, rx_status); =2D kfree(rx_status); break; case ieee80211_tx_status_msg: /* get pointer to saved status out of skb->cb */ --nextPart2647275.Geb85LW4o3 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQBFy//DT3Oqt9AH4aERAhcJAJ0dj1PM+iYA84AgLEvrZbU7Z71MnQCfWF1K ZmeiVkkcFWQ9pCmNU2ZjMTY= =B3f3 -----END PGP SIGNATURE----- --nextPart2647275.Geb85LW4o3-- -: To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@vger.kernel.org: More majordomo info at http: //vger.kernel.org/majordomo-info.html