To: Greg KH <gregkh@suse.de>
Cc: "Bryan O'Sullivan" <bos@pathscale.com>, rolandd@cisco.com, akpm@osdl.org,
       davem@davemloft.net, linux-kernel@vger.kernel.org,
       openib-general@openib.org
Subject: Re: [PATCH 8 of 20] ipath - sysfs support for core driver
References: <patchbomb.1141950930@eng-12.pathscale.com>
	<1123028ac13ac1de2457.1141950938@eng-12.pathscale.com>
	<20060310011106.GD9945@suse.de>
	<1141967377.14517.32.camel@camp4.serpentine.com>
	<20060310063724.GB30968@suse.de>
From: Roland Dreier <rdreier@cisco.com>
Date: Fri, 10 Mar 2006 06:59:15 -0800
Message-ID: <adairqmbb24.fsf@cisco.com>
User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.18 (linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 794
Lines: 18

    Greg> The main issue is that if you create a sysfs file like this,
    Greg> and then in 3 months realize that you need to change one of
    Greg> those characters to be something else, you are in big
    Greg> trouble...

I think that PortInfo and NodeInfo might be fair game for sysfs files,
because they are actually defined in the IB spec with a binary format
that is sent on the wire.  So they're not going to change.

On the other hand it's not clear to me why using that wire protocol as
an interface to userspace is a good idea...

 - R.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/