[lkml]   [1999]   [Mar]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Linux/IA-64 byte order
Oren Laadan writes:
> Hi,
> > > Make an empty map for little-endian direct access and make a backing
> > > map with theactual file. Then install a signal handler to catch
> > > reads in the empty map, copy a page (or more) with byteswapping, and
> > > you're done. "Loading" is still extremely fast.
> >
> > Yes, "loading" a subsection of the data is still (fairly) fast. But
> > that doesn't solve the other problem: huge swap space consumption when
> > you want to access the entire dataset. It's often the case that you
> > have much more data disc than you have swap disc.
> How about this simple solution - write/use a utility which converts
> the data file from BE to LE (once for every file) ? (of course, you
> would need to know the exact structure of the binary data in the
> file for that).

You're talking about doubling the disc storage requirements. The
software which wrote the data is also going to be used to do some
analysis, so the user needs to keep that version around.

> This worked for me when I needed to compile and execute applications
> that used to run on Sparc, and required the original binary data
> files :-)

Experience has showed that users don't like these extra steps. It has
to be transparent. And transparently writing out a byte swapped copy
of the data is not going to be received well, either.



To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:50    [W:0.121 / U:3.188 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site