Skip to contentSkip to conversation

hippi: change to not use skb private

RFC In review Stephen Hemminger 2 participants 4 messages Sep 13, 2005 – Sep 15, 2005

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

RFC 1/1 hippi: change to not use skb private

It looks like the following would fix hippi to not have to put fields in sk_buff. The ifield looks appears to to be additional header information that is being passed in the skb but could just be put in the header.

Does anyone still have the hardware to test this? Is anyone even using it on 2.6?

drivers/net/rrunner.c +1 -25
Index: hippi-2.6.13/drivers/net/rrunner.c
===================================================================
@@ -1432,7 +1432,6 @@ static int rr_start_xmit(struct sk_buff 
 	struct ring_ctrl *txctrl;
 	unsigned long flags;
 	u32 index, len = skb->len;
-	u32 *ifield;
 	struct sk_buff *new_skb;
 
 	if (readl(&regs->Mode) & FATAL_ERR)
@@ -1440,29 +1439,6 @@ static int rr_start_xmit(struct sk_buff 
 		       readl(&regs->Fail1), readl(&regs->Fail2));
 
 	/*
-	 * We probably need to deal with tbusy here to prevent overruns.
-	 */
-
-	if (skb_headroom(skb) < 8){
-		printk("incoming skb too small - reallocating\n");
-		if (!(new_skb = dev_alloc_skb(len + 8))) {
-			dev_kfree_skb(skb);
-			netif_wake_queue(dev);
-			return -EBUSY;
-		}
-		skb_reserve(new_skb, 8);
-		skb_put(new_skb, len);
-		memcpy(new_skb->data, skb->data, len);
-		dev_kfree_skb(skb);
-		skb = new_skb;
-	}
-
-	ifield = (u32 *)skb_push(skb, 8);
-
-	ifield[0] = 0;
-	ifield[1] = skb->private.ifield;
-
-	/*
 	 * We don't need the lock before we are actually going to start
 	 * fiddling with the control blocks.
 	 */
@@ -1475,7 +1451,7 @@ static int rr_start_xmit(struct sk_buff 
 	rrpriv->tx_skbuff[index] = skb;
 	set_rraddr(&rrpriv->tx_ring[index].addr, pci_map_single(
 		rrpriv->pci_dev, skb->data, len + 8, PCI_DMA_TODEVICE));
-	rrpriv->tx_ring[index].size = len + 8; /* include IFIELD */
+	rrpriv->tx_ring[index].size = len;
 	rrpriv->tx_ring[index].mode = PACKET_START | PACKET_END;
 	txctrl->pi = (index + 1) % TX_RING_ENTRIES;
 	wmb();
include/linux/skbuff.h +1 -6
Index: hippi-2.6.13/include/linux/skbuff.h
===================================================================
@@ -194,7 +194,6 @@ struct skb_shared_info {
  *	@nfct: Associated connection, if any
  *	@nfctinfo: Relationship of this skb to the connection
  *	@nf_bridge: Saved data about a bridged frame - see br_netfilter.c
- *      @private: Data which is private to the HIPPI implementation
  *	@tc_index: Traffic control index
  *	@tc_verd: traffic control verdict
  *	@tc_classid: traffic control classid
@@ -267,11 +266,7 @@ struct sk_buff {
 	struct nf_bridge_info	*nf_bridge;
 #endif
 #endif /* CONFIG_NETFILTER */
-#if defined(CONFIG_HIPPI)
-	union {
-		__u32		ifield;
-	} private;
-#endif
+
 #ifdef CONFIG_NET_SCHED
        __u32			tc_index;        /* traffic control index */
 #ifdef CONFIG_NET_CLS_ACT
net/802/hippi.c +9 -7
Index: hippi-2.6.13/net/802/hippi.c
===================================================================
@@ -50,7 +50,8 @@ static int hippi_header(struct sk_buff *
 			unsigned short type, void *daddr, void *saddr,
 			unsigned len)
 {
-	struct hippi_hdr *hip = (struct hippi_hdr *)skb_push(skb, HIPPI_HLEN);
+	struct hippi_hdr *hip = (struct hippi_hdr *)skb_push(skb, HIPPI_HLEN + 8);
+	u32 *ifield = (u32 *) (hip + 1);
 
 	if (!len){
 		len = skb->len - HIPPI_HLEN;
@@ -81,13 +82,14 @@ static int hippi_header(struct sk_buff *
 	hip->snap.oui[2]	= 0x00;
 	hip->snap.ethertype	= htons(type);
 
-	if (daddr)
-	{
+	memset(ifield, 0, 2*sizeof(u32));
+	if (daddr) {
 		memcpy(hip->le.dest_switch_addr, daddr + 3, 3);
-		memcpy(&skb->private.ifield, daddr + 2, 4);
-		return HIPPI_HLEN;
+		memcpy(ifield+1, daddr + 2, 4);
+		return HIPPI_HLEN + 8;
 	}
-	return -((int)HIPPI_HLEN);
+
+	return -((int)HIPPI_HLEN - 8);
 }
 
 
@@ -200,7 +202,7 @@ static void hippi_setup(struct net_devic
 	 * still need a fake ARPHRD to make ifconfig and friends play ball.
 	 */
 	dev->type		= ARPHRD_HIPPI;
-	dev->hard_header_len 	= HIPPI_HLEN;
+	dev->hard_header_len 	= HIPPI_HLEN + 8;
 	dev->mtu		= 65280;
 	dev->addr_len		= HIPPI_ALEN;
 	dev->tx_queue_len	= 25 /* 5 */;
net/core/skbuff.c +0 -3
Index: hippi-2.6.13/net/core/skbuff.c
===================================================================
@@ -370,9 +370,6 @@ struct sk_buff *skb_clone(struct sk_buff
 	nf_bridge_get(skb->nf_bridge);
 #endif
 #endif /*CONFIG_NETFILTER*/
-#if defined(CONFIG_HIPPI)
-	C(private);
-#endif
 #ifdef CONFIG_NET_SCHED
 	C(tc_index);
 #ifdef CONFIG_NET_CLS_ACT
maintainer
#1 lore raw

From: Stephen Hemminger <[email protected]>
Date: Tue, 13 Sep 2005 11:38:58 -0700

Quoted 4 lines

It looks like the following would fix hippi to not have to put fields in sk_buff. The ifield looks appears to to be additional header information that is being passed in the skb but could just be put in the header.

I can't see any problem with this patch, and it fixes all the realloc stuff that has to potentially occur in the transmit path.

maintainer
#2 lore raw
In reply to Stephen Hemminger

From: Stephen Hemminger <[email protected]>
Date: Tue, 13 Sep 2005 11:38:58 -0700

Quoted 4 lines

It looks like the following would fix hippi to not have to put fields in sk_buff. The ifield looks appears to to be additional header information that is being passed in the skb but could just be put in the header.

Stephen this patch is against 2.6.13 or something. We already put this thing into a SKB control block for 2.6.14-rc1. Do you want to keep things that way or update your patch for 2.6.14-rc1?

#3 lore raw
Quoted 11 lines · On Wed, 14 Sep 2005 21:03:16 -0700 (PDT) "David S. Miller"…

From: Stephen Hemminger <[email protected]>
Date: Tue, 13 Sep 2005 11:38:58 -0700

Quoted 4 lines

It looks like the following would fix hippi to not have to put fields in sk_buff. The ifield looks appears to to be additional header information that is being passed in the skb but could just be put in the header.

Stephen this patch is against 2.6.13 or something. We already put this thing into a SKB control block for 2.6.14-rc1. Do you want to keep things that way or update your patch for 2.6.14-rc1?

Sorry, I was cleaning up the old unfinished work pile. The new version (using header) is better than the cb version because it is cleaner and doesn't have the nasty error handling issues of reallocating header in the transmit routine.