netdev
[Top] [All Lists]

Re: [PATCH] convering bonding driver /proc interface to seq_file

To: James Morris <jmorris@xxxxxxxxxxxxxxxx>
Subject: Re: [PATCH] convering bonding driver /proc interface to seq_file
From: Shmulik Hen <shmulik.hen@xxxxxxxxx>
Date: Sun, 24 Aug 2003 20:12:58 +0300
Cc: <bonding-devel@xxxxxxxxxxxxxxxxxxxxx>, <netdev@xxxxxxxxxxx>
In-reply-to: <Mutt.LNX.4.44.0308250112470.21951-100000@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Organization: Intel corp.
References: <Mutt.LNX.4.44.0308250112470.21951-100000@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: shmulik.hen@xxxxxxxxx
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: KMail/1.4.3
On Sunday 24 August 2003 06:15 pm, James Morris wrote:
>
> Can you provide a pointer to this code?
>

Please see my email from August 8th with subject:
"[SET 1][PATCH 3/6][bonding] backport 2.6 changes to 2.4"
sent to netdev@xxxxxxxxxxx and bonding-devel@xxxxxxxxxxxxxxxxxxxxxx

> seq_file is the standard and preferred way to do this kind of
> thing.

Yes, we know. We wanted to convert to seq_file too, but as it turns 
out, in order to create a separate proc file for each bond device you 
need to use the PDE(inode) macro which doesn't exist in 2.4 yet. 
Since we wanted to maintain compatibility in the bonding module 
between 2.4 and 2.6 as much as possible, we figured that as a first 
step we'll start using bond_read_proc() instead of bond_get_info() to 
allow just that.

BTW, we really like the change from /proc/net/bond0/info to 
/proc/net/bonding/bond0. We thought we'll add that into our cleanup 
patch set that should come out once the back porting set is accepted.

-- 
| Shmulik Hen   Advanced Network Services  |
| Israel Design Center, Jerusalem          |
| LAN Access Division, Platform Networking |
| Intel Communications Group, Intel corp.  |


<Prev in Thread] Current Thread [Next in Thread>