|
»
»
Building on the z50
|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
 |
Building on the z50
by Scott Lawrence-4
::
Rate this Message:
Hey all.
I use my z50 as a portable development machine. It works great. Awesome keyboard, excellent battery life, etc. One thing though; the drive access times to the CF card are painful, due to PIO access times. Does anyone have any configuration suggestions wrt this? I was thinking that a 5 or 10 meg ramdisk would be great; have gcc put its build files out there, or possibly have the source files copied out there, then just refreshed back to the CF every so often. (whatever) Anyone have suggestions on how to get a ramdisk/partition to be configured? I tried to do it a few months back, with no good results. -s -- Scott Lawrence yorgle@... |
|
|
Re: Building on the z50
by jscottkasten
::
Rate this Message:
Have you tried enabling softdep? That is probably the one single largest improvement you can make. It may ultimately make you flash live a bit longer too.
-S- --- On Wed, 10/7/09, Scott Lawrence <yorgle@...> wrote: > From: Scott Lawrence <yorgle@...> > Subject: Building on the z50 > To: "hpcmips NetBSD mailing list" <port-hpcmips@...> > Date: Wednesday, October 7, 2009, 7:17 AM > Hey all. > > I use my z50 as a portable development machine. It > works great. > Awesome keyboard, excellent battery life, etc. > > One thing though; the drive access times to the CF card are > painful, > due to PIO access times. > > Does anyone have any configuration suggestions wrt > this? I was > thinking that a 5 or 10 meg ramdisk would be great; have > gcc put its > build files out there, or possibly have the source files > copied out > there, then just refreshed back to the CF every so often. > (whatever) > > Anyone have suggestions on how to get a ramdisk/partition > to be configured? > > I tried to do it a few months back, with no good results. > > -s > > -- > Scott Lawrence > yorgle@... > |
|
|
Re: Building on the z50
by Scott Lawrence-4
::
Rate this Message:
How do I do this? I'm not building my own kernel or anything; just
using downloaded stuff from the main distribution -s On Wed, Oct 7, 2009 at 2:45 PM, <jscottkasten@...> wrote: > Have you tried enabling softdep? That is probably the one single largest improvement you can make. It may ultimately make you flash live a bit longer too. > > -S- > > --- On Wed, 10/7/09, Scott Lawrence <yorgle@...> wrote: > >> From: Scott Lawrence <yorgle@...> >> Subject: Building on the z50 >> To: "hpcmips NetBSD mailing list" <port-hpcmips@...> >> Date: Wednesday, October 7, 2009, 7:17 AM >> Hey all. >> >> I use my z50 as a portable development machine. It >> works great. >> Awesome keyboard, excellent battery life, etc. >> >> One thing though; the drive access times to the CF card are >> painful, >> due to PIO access times. >> >> Does anyone have any configuration suggestions wrt >> this? I was >> thinking that a 5 or 10 meg ramdisk would be great; have >> gcc put its >> build files out there, or possibly have the source files >> copied out >> there, then just refreshed back to the CF every so often. >> (whatever) >> >> Anyone have suggestions on how to get a ramdisk/partition >> to be configured? >> >> I tried to do it a few months back, with no good results. >> >> -s >> >> -- >> Scott Lawrence >> yorgle@... >> > -- Scott Lawrence yorgle@... |
|
|
Re: Building on the z50
by jscottkasten
::
Rate this Message:
Most of the NetBSD release kernels have softdep added to the build config, so it is only necessary to turn it on in the run time. Just add the magic to the /etc/fstab like so:
http://www.netbsd.org/docs/misc/#softdeps While you're in there, you might also check to make sure you have the noatime and nodevmtime options enabled as well. This combination of things will ensure the minimum number of writes to the storage for general use. You mentioned compiling stuff. You could also try adding "-pipe" to CFLAGS when you run configure for your package. This will reduce the compiler's reliance on temporary files at the expense of needing more system memory to run. This may be less painful, and more efficient than making /tmp a memory based file system. All this stuff together will probably give you that 15 - 20% advantage you're looking for. -S- --- On Wed, 10/7/09, Scott Lawrence <yorgle@...> wrote: > From: Scott Lawrence <yorgle@...> > Subject: Re: Building on the z50 > To: jscottkasten@... > Cc: "hpcmips NetBSD mailing list" <port-hpcmips@...> > Date: Wednesday, October 7, 2009, 11:46 AM > How do I do this? I'm not > building my own kernel or anything; just > using downloaded stuff from the main distribution > > -s > > On Wed, Oct 7, 2009 at 2:45 PM, <jscottkasten@...> > wrote: > > Have you tried enabling softdep? That is probably > the one single largest improvement you can make. It may > ultimately make you flash live a bit longer too. > > > > -S- > > > > --- On Wed, 10/7/09, Scott Lawrence <yorgle@...> > wrote: > > > >> From: Scott Lawrence <yorgle@...> > >> Subject: Building on the z50 > >> To: "hpcmips NetBSD mailing list" <port-hpcmips@...> > >> Date: Wednesday, October 7, 2009, 7:17 AM > >> Hey all. > >> > >> I use my z50 as a portable development machine. > It > >> works great. > >> Awesome keyboard, excellent battery life, etc. > >> > >> One thing though; the drive access times to the CF > card are > >> painful, > >> due to PIO access times. > >> > >> Does anyone have any configuration suggestions > wrt > >> this? I was > >> thinking that a 5 or 10 meg ramdisk would be > great; have > >> gcc put its > >> build files out there, or possibly have the source > files > >> copied out > >> there, then just refreshed back to the CF every so > often. > >> (whatever) > >> > >> Anyone have suggestions on how to get a > ramdisk/partition > >> to be configured? > >> > >> I tried to do it a few months back, with no good > results. > >> > >> -s > >> > >> -- > >> Scott Lawrence > >> yorgle@... > >> > > > > > > -- > Scott Lawrence > yorgle@... > |
|
|
Re: Building on the z50
by Scott Lawrence-4
::
Rate this Message:
Excellent. I will try these suggestions!
Thanks! -s On Wed, Oct 7, 2009 at 3:01 PM, <jscottkasten@...> wrote: > Most of the NetBSD release kernels have softdep added to the build config, so it is only necessary to turn it on in the run time. Just add the magic to the /etc/fstab like so: > > http://www.netbsd.org/docs/misc/#softdeps > > While you're in there, you might also check to make sure you have the noatime and nodevmtime options enabled as well. This combination of things will ensure the minimum number of writes to the storage for general use. > > You mentioned compiling stuff. You could also try adding "-pipe" to CFLAGS when you run configure for your package. This will reduce the compiler's reliance on temporary files at the expense of needing more system memory to run. This may be less painful, and more efficient than making /tmp a memory based file system. > > All this stuff together will probably give you that 15 - 20% advantage you're looking for. > > -S- > > --- On Wed, 10/7/09, Scott Lawrence <yorgle@...> wrote: > >> From: Scott Lawrence <yorgle@...> >> Subject: Re: Building on the z50 >> To: jscottkasten@... >> Cc: "hpcmips NetBSD mailing list" <port-hpcmips@...> >> Date: Wednesday, October 7, 2009, 11:46 AM >> How do I do this? I'm not >> building my own kernel or anything; just >> using downloaded stuff from the main distribution >> >> -s >> >> On Wed, Oct 7, 2009 at 2:45 PM, <jscottkasten@...> >> wrote: >> > Have you tried enabling softdep? That is probably >> the one single largest improvement you can make. It may >> ultimately make you flash live a bit longer too. >> > >> > -S- >> > >> > --- On Wed, 10/7/09, Scott Lawrence <yorgle@...> >> wrote: >> > >> >> From: Scott Lawrence <yorgle@...> >> >> Subject: Building on the z50 >> >> To: "hpcmips NetBSD mailing list" <port-hpcmips@...> >> >> Date: Wednesday, October 7, 2009, 7:17 AM >> >> Hey all. >> >> >> >> I use my z50 as a portable development machine. >> It >> >> works great. >> >> Awesome keyboard, excellent battery life, etc. >> >> >> >> One thing though; the drive access times to the CF >> card are >> >> painful, >> >> due to PIO access times. >> >> >> >> Does anyone have any configuration suggestions >> wrt >> >> this? I was >> >> thinking that a 5 or 10 meg ramdisk would be >> great; have >> >> gcc put its >> >> build files out there, or possibly have the source >> files >> >> copied out >> >> there, then just refreshed back to the CF every so >> often. >> >> (whatever) >> >> >> >> Anyone have suggestions on how to get a >> ramdisk/partition >> >> to be configured? >> >> >> >> I tried to do it a few months back, with no good >> results. >> >> >> >> -s >> >> >> >> -- >> >> Scott Lawrence >> >> yorgle@... >> >> >> > >> >> >> >> -- >> Scott Lawrence >> yorgle@... >> > -- Scott Lawrence yorgle@... |
|
|
Re: Building on the z50
by Juergen Sell
::
Rate this Message:
If you have working network, create an openvpn tunnel to your trusted machine and use distcc with a cross-compiler.
You get the cross-compiler from the bsd-kernel build environment, for openvpn follow standard procedure, distcc setup is explained in the docs. I found this setup best, because it keeps the build environment on the mipsel target machine, thus dependencies and system checks work as expected. Just time consuming compile is being offloaded to another work horse. Works like a charme for pkgsrc and other packages and for me resulted in usable vs. unbearable. HTH, js 2009/10/7 Scott Lawrence <yorgle@...> Hey all. |
| Free embeddable forum powered by Nabble | Forum Help |
