| To: | "Ralf Baechle" <ralf@xxxxxxxxxxx>, "John Hawkes" <hawkes@xxxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: unsigned long jiffies |
| From: | "John Hawkes" <hawkes@xxxxxxxxxxxxxxxxxxxx> |
| Date: | Mon, 22 May 2000 15:42:49 -0700 |
| Cc: | "linux-origin" <linux-origin@xxxxxxxxxxx> |
| References: | <059901bfc43b$866bf5c0$1d70eea9@seattle.sgi.com> <20000523003706.B6425@uni-koblenz.de> |
| Sender: | owner-linux-origin@xxxxxxxxxxx |
> About which proc-file are we talking? In general you should probably > just design the file's format such that it can be parsed unambiguously; > generally there ASCII files are somewhat preffered. /proc/lockmeter I'm reluctant to use an ASCII formatting, since the heavy-duty data transfers involve hundreds, if not thousands, of data values. The first problem I stumbled over was in a general information header. The Big Data arrays are more clearly typed as 32-bit data. John |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: unsigned long jiffies, Ralf Baechle |
|---|---|
| Next by Date: | Re: compiler bug?, John Hawkes |
| Previous by Thread: | Re: unsigned long jiffies, Ralf Baechle |
| Next by Thread: | Re: compiler bug?, John Hawkes |
| Indexes: | [Date] [Thread] [Top] [All Lists] |