* Re: PATCH: (as177) Add class_device_unregister_wait() and platform_device_unregister_wait() to the driver model core
From: Valdis.Kletnieks @ 2004-01-26 6:25 UTC (permalink / raw)
To: Steve Youngs; +Cc: Linux Kernel List
In-Reply-To: <microsoft-free.87d697s18l.fsf@eicq.dnsalias.org>
[-- Attachment #1: Type: text/plain, Size: 487 bytes --]
On Mon, 26 Jan 2004 15:55:06 +1000, Steve Youngs <sryoungs@bigpond.net.au> said:
> Because the 2nd user is still using the module so its in-use bit
> should still be set. Remember that when the module was first loaded
> it registered a function with the kernel for testing whether the
> module is in use.
Anybody who's ever been in a bathroom stall and somebody turned off the
lights on their way out will intuitively understand why you need a reference
count and not an in-use bit,
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply
* ax25 support in aprsd
From: Adi Linden @ 2004-01-26 6:25 UTC (permalink / raw)
To: linux-hams
I am trying to get aprsd to work with ax25 support. But documentations
seems to be non existant. Any pointers on how to do it?
I'd like to eventually run digi_ned as digi and aprsd as igate on the same
machine.
Thanks,
Adi
^ permalink raw reply
* [uml-devel] Swapping directly to host swap area?
From: William Stearns @ 2004-01-25 23:34 UTC (permalink / raw)
To: ML-uml-devel; +Cc: William Stearns
Good evening, Jeff, all,
Please feel free to file this in the "Damn, I wish Bill would
read kernel source and get a clue" category if appropriate... :-)
When a VM needs to swap out, is there some way the UML kernel
could send that sector directly to the host swap area instead of running
its own swap? In the current setup, the host kernel sees this as a normal
write to an open file, caching it in the process and so not truly freeing
up the ram for a bit. If the UML swapout routine handed the sector to the
host swapout routine, it might get freed faster.
I don't _see_ this as a security concern; only root on the host
could read the host swap directly; if anything this looks more secure than
the swap file readable by the user under which uml runs on the host.
Again, my apologies if my random ravings have no value in the real
world. Feel free to respond with nothing more than "not useful". :-)
Cheers,
- Bill
---------------------------------------------------------------------------
"Got me an office; I'm there late at night.
Just send me e-mail, maybe I'll write."
-- Joe Walsh for the 21st Century
(Courtesy of Bruce Tong <zztong@laxmi.ev.net>)
--------------------------------------------------------------------------
William Stearns (wstearns@pobox.com). Mason, Buildkernel, freedups, p0f,
rsync-backup, ssh-keyinstall, dns-check, more at: http://www.stearns.org
--------------------------------------------------------------------------
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
^ permalink raw reply
* Re: [ANNOUNCE] Cooperative Linux
From: Karim Yaghmour @ 2004-01-26 6:36 UTC (permalink / raw)
To: Nuno Silva; +Cc: JustFillBug, linux-kernel
In-Reply-To: <4014A058.9080206@vgertech.com>
Nuno Silva wrote:
> That's xen. You can learn more here:
>
> http://www.cl.cam.ac.uk/Research/SRG/netos/xen/
For a UP system, Xen may be fine, depending on what you're trying to
do. If you're looking for a better VMware, then Xen is likely to fit
your bill. However, there are a few things to keep in mind when
looking at this sort of stuff. So, for example, Xen assumes that all
OSes are going to use the same devices for I/O: same disk, same
NIC, etc. It therefore implements lots of virtual devices for these.
But what if you wanted each OS to manage separate hardware? Also,
I'm not sure I want my OS instances to have to request memory on
a page basis with the nanokernel/monitor. Wouldn't it be just better
to reuse the existing work on the hotplug hardware (hotplug CPU,
hotplug memory, etc.) to have the kernels get/return hardware
resources to the nanokernel? Also, how generic is the virtualization
solution being examined? I've put some thought into getting a
virtualization architecture which spans UP, SMP, SMP-clusters, and
hard-rt, and wrote that down as a series of papers about Adeos. I
probably don't have the final answer, and there are probably many
things I haven't figured out in the papers I've written on the topic,
but you may want to take a look.
Karim
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546
^ permalink raw reply
* Re: packet/soundmodem questions
From: James Washer @ 2004-01-26 6:33 UTC (permalink / raw)
To: n7bfs; +Cc: linux-hams
In-Reply-To: <200401251943.35916.n7bfs@qwest.net>
I'm sure you can load it as a module.. I chose to build it into the kernel.
- jim
On Sun, 25 Jan 2004 19:43:35 -0800
"Douglas Cole" <n7bfs@qwest.net> wrote:
> On Sunday 25 January 2004 19:08, James Washer wrote:
> > The soundmodem setup was relatively simple. All worked fine on my desktop
> > box. I'm got an issue with the laptop transmitting, but I'm sure I'll get
> > around that.
> >
> > Compile a kernel with AX.25, AX.25 Level2, and MKISS, then run soundmodem
> > in userland.
>
> Umm I was under the assumption that I could load AX25 as a module under
> SuSE...
>
> Is it required to compile AX25 into the kernel as you mention? or is it ok to
> load as a module?
>
> Also will soundmodem run while I am running ALSA/ARTS on my X session ?
>
> tnx for the input :)
>
> Doug
>
> >
> > If you follow the directions EXACTLY for building and installing the AX.25
> > tools, apps, and library ( make sure to do the 'make installconf' step )
> > everything pretty well falls into place.
> >
> > Write if you hit a snag.
> >
> > - jim
> >
> > On Sun, 25 Jan 2004 17:50:47 -0800
> >
> > "Douglas Cole" <n7bfs@qwest.net> wrote:
> > > On Sunday 25 January 2004 15:08, James Washer wrote:
> > > > I've been working on this very issue for a couple of days on my IBM
> > > > X600 thinkpad, and will give it a shot soon on my T21.
> > > >
> > > > So far, the receive is fine, but I'm not transmitting yet. The
> > > > soundcard is only producing what sounds like framing bits.. No data
> > > > yet.
> > > >
> > > > If you installed the AX.25 tools package, just do 'man -k AX.25' to see
> > > > a list of tools that were installed.
> > > >
> > > > Keep in touch with how things are going on your T23.
> > > >
> > > > - jim
> > >
> > > Thanks James for the input, I was hoping to get some input ala userland
> > > style as I am not experienced in the Linux packet realm, so it appears
> > > that I have lots of reading to do, since when I did the man command you
> > > provided above it listed a mass of entries that I am totally unfamiliar
> > > with...
> > >
> > > It may be easier for me to just go buy a used tnc, but then again where
> > > is the fun in that ? ;^}
> > >
> > > I will try to share my experiences with my T23 once I get an idea of
> > > where "square one" is...
> > >
> > > 73
> > >
> > > Doug
> > >
> > > > On Sun, 25 Jan 2004 11:59:28 -0800
> > > >
> > > > "Douglas Cole" <n7bfs@qwest.net> wrote:
> > > > > Have been following the list for a while now and got interested in
> > > > > the soundmodem thread...
> > > > >
> > > > > I too would like to get soundmodem up and running so as to be able to
> > > > > run 1200 baud packet from my laptop (IBM thinkpad T23) and have done
> > > > > a small amount of searching but have not found any documentation on
> > > > > soundmodem, or at least so little that it leaves me wondering how to
> > > > > make things work...
> > >
> > >
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply
* Re: 2.6.2-rc1-mm2 kernel oops
From: Eric @ 2004-01-26 6:33 UTC (permalink / raw)
To: Andrew Morton, sboyce, linux-kernel, bunk, torvalds
In-Reply-To: <20040125160400.5b9d2e88.akpm@osdl.org>
On Sunday 25 January 2004 18:04, Andrew Morton wrote:
> Andrew Morton <akpm@osdl.org> wrote:
> > Eric <eric@cisu.net> wrote:
> > > Now I get the test_wp_bit oops w/
> >
> Can you see if this patch makes the test_wp_bit() oops go away?
I will try it tomorrow. Sorry I am a little slow on the e-mails, I will do
what I can to help, but I can't move as fast, or devote as much time as I
would like, im in college right now. I will apply the patch and see if it
makes my oops go away.
Thanks so much for your help. I appreciate all the hard work you guys do on
the kernel and all the mind-racking problems that come with an
ever-increasing userbase.
-------------------------
Eric Bambach
Eric at cisu dot net
-------------------------
^ permalink raw reply
* Re: Q: Filesystem choice..
From: David Woodhouse @ 2004-01-26 6:42 UTC (permalink / raw)
To: Eric W. Biederman; +Cc: linux-mtd
In-Reply-To: <m3u12jr8y4.fsf@maxwell.lnxi.com>
On Sun, 2004-01-25 at 14:53 -0700, Eric W. Biederman wrote:
> The old papers on jffs2 would make it unacceptable as it reserves
> 5 erase blocks.
It's got slightly different heuristics now -- a proportion of total
size, plus a proportion of total _blocks_. That was done primarily to
deal with NAND flash, where we need _more_ blocks reserved, but it
should also have helped with small NOR flashes.
You blatantly don't _need_ to reserve five erase blocks to let you
rewrite the contents of the remaining, erm, one erase block full of
data. You can tune this; it's not a mount option but it's relatively
simple to change in the code.
> And I don't know if yaffs or yaffs2 is any better.
They're for NAND, not NOR flash.
> In addition boot time is important so it would be ideal if I did not
> to read every byte of the ROM chip to initialize the filesystem.
There have been efforts to improve JFFS2 performance in this respect. It
still reads the _header_ from each node of the file system, but doesn't
actually checksum every node any more.
--
dwmw2
^ permalink raw reply
* Re: WP 5.1, graphical preview, in console
From: Justin Zygmont @ 2004-01-26 6:48 UTC (permalink / raw)
To: Rob Ristroph; +Cc: linux-msdos
In-Reply-To: <87oesrbbfk.fsf@rgristroph-austin.ath.cx>
On 25 Jan 2004, Rob Ristroph wrote:
> >>>>> "Justin" == Justin Zygmont <jzygmont@solarflow.dyndns.org> writes:
> Justin>
> Justin> did you set your $_console=1 and $_graphics=1 in dosemu.conf?
>
> Yes. Actually it is conf/dosemurc in the precompiled distribution. I
> also set $_video = "vga", $_rawkeyboard = (1), $_vbios_post = (1),
> $_chipset = "ati" and also tried $_chipset = "plainvga", and various
> combinations of those.
>
> Does graphics from the console work for you ? Are you using the
> binary distribution, or did you compile it from source ? If so, did
> you edit compiletime-settings at all ?
not sure about wp 5.1 but console graphics work for most programs for me.
I compiled my own, but I don't see why that should really matter. I have
a custom download you can try if you want to see: ftp://solarflow.dyndns.org
How about xdosemu? if that won't do the graphics, I don't know what will.
^ permalink raw reply
* [uml-devel] Re: tt mode tls/glibc crash with 2.6 (Was: Re: uml-patch-2.6.0)
From: M A Young @ 2004-01-23 23:52 UTC (permalink / raw)
To: Ingo Molnar; +Cc: Jeff Dike, Gerd Knorr, user-mode-linux-devel
In-Reply-To: <Pine.LNX.4.58.0401232125410.8188@vega.dur.ac.uk>
On Fri, 23 Jan 2004, M A Young wrote:
> I now know where 0xbeffe018 comes from. The endless segfault is triggered
> from line 1256 of elf/rtld.c in the glibc code (1252-1258 are shown from
> RedHat's glibc-2.3.2-101.4.i686.rpm package)
>
> #ifdef NEED_DL_SYSINFO
> if (GL(dl_sysinfo_dso) != NULL)
> {
> /* We have a prelinked DSO preloaded by the system. */
> GL(dl_sysinfo) = GL(dl_sysinfo_dso)->e_entry;
>
> /* Do an abridged version of the work _dl_map_object_from_fd would do
>
>
> GL(dl_sysinfo_dso) is _dl_sysinfo_dso, _rtld_local._dl_sysinfo_dso or
> _rtld_global._dl_sysinfo_dso according to context
>
> _dl_sysinfo_dso=0 is at 0xa0603f50
> _rtld_local._dl_sysinfo_dso=0xbeffe000 is at 0x40015454
> _rtld_global._dl_sysinfo_dso=0xbeffe000 is at 0x40015454
>
> so I am guessing that _rtld_{local,global}._dl_sysinfo_dso should have
> been initialized from _dl_sysinfo_dso but wasn't. This could be a glibc
> bug, though I haven't looked closely enough to be sure.
Further checking shows that _rtld_global._dl_sysinfo_dso is set from the
value of AT_SYSINFO_EHDR passed by the kernel. So UML tt mode is broken
because it doesn't seem to pass this value. However glibc is also broken,
because it should set _rtld_global._dl_sysinfo_dso=NULL by default in case
AT_SYSINFO_EHDR isn't passed to it by the kernel.
Anyway, I intend to test whether this is the problem tomorrow, either by
recompiling glibc (it is a one-line fix), or possibly using a hex editor
to hack the existing ld.so.
Michael Young
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
^ permalink raw reply
* latest 2.6 patch for dpt_i20 driver
From: Karen Shaeffer @ 2004-01-26 6:58 UTC (permalink / raw)
To: linux-scsi
Hi,
I have access to several Adaptec I2O RAID controllers and am interested in
running linux-2.6.x kernels in this lab for testing purposes. Will someone
please advise me on where to find the most up to date patch(es) for this
driver. Thanks in advance.
Karen
--
Karen Shaeffer
Neuralscape, Palo Alto, Ca. 94306
shaeffer@neuralscape.com http://www.neuralscape.com
^ permalink raw reply
* RE: [linux-lvm] First try, first fail with LVM.
From: Roger Eriksson @ 2004-01-26 7:00 UTC (permalink / raw)
To: linux-lvm
In-Reply-To: <20040116111752.GF2837@redhat.com>
Thank you for answereing.
It turned out to be a problem with the power supply as it couldn't output
enough power to run six farly new disks (3 IDE & 3 SCSI) . Eight old disk
worked just fine (3 + 5) though.
I managed to restore most of the data from the NTFS file systems so I
decided to reinstall the Linux server and run some tests with it and found
out about the power problem. Always troble with the same disk but when I
moved it to another computer and ran Maxtor's hard disk test program several
times and no problems. I will still be a bit suspicious about it though,
until it's proven itself..
Thanks again.
^ permalink raw reply
* Re: NVidia and 2.6.1
From: Christian Unger @ 2004-01-26 7:07 UTC (permalink / raw)
To: Linux Kernel List
Hi
Sorry - lost the topic of the email.
Anyways, i am currently running the 5328 version of the NVidia drivers
(pre-patched).
Thank you all for your patience and help.
How was it resolved? I formated and started from scratch. Not elegant, but it
worked. Dunno what the real problem was, but it's over and my card is
working ... Hurrah ...
--
with kind regards,
Christian Unger
^ permalink raw reply
* Re: Q: Filesystem choice..
From: Eric W. Biederman @ 2004-01-26 7:09 UTC (permalink / raw)
To: David Woodhouse; +Cc: linux-mtd
In-Reply-To: <1075099329.17157.97.camel@lapdancer.baythorne.internal>
David Woodhouse <dwmw2@infradead.org> writes:
> On Sun, 2004-01-25 at 14:53 -0700, Eric W. Biederman wrote:
> > The old papers on jffs2 would make it unacceptable as it reserves
> > 5 erase blocks.
>
> It's got slightly different heuristics now -- a proportion of total
> size, plus a proportion of total _blocks_. That was done primarily to
> deal with NAND flash, where we need _more_ blocks reserved, but it
> should also have helped with small NOR flashes.
>
> You blatantly don't _need_ to reserve five erase blocks to let you
> rewrite the contents of the remaining, erm, one erase block full of
> data. You can tune this; it's not a mount option but it's relatively
> simple to change in the code.
Has anyone gotten as far as a proof. Or are there some informal
things that almost make up a proof, so I could get a feel? Reserving
more than a single erase block is going to be hard to swallow for such
a small filesystem.
> > And I don't know if yaffs or yaffs2 is any better.
>
> They're for NAND, not NOR flash.
I think I have heard about a port to NOR flash, but tuned
for NAND flash I would be really surprised if they were different.
> > In addition boot time is important so it would be ideal if I did not
> > to read every byte of the ROM chip to initialize the filesystem.
>
> There have been efforts to improve JFFS2 performance in this respect. It
> still reads the _header_ from each node of the file system, but doesn't
> actually checksum every node any more.
That should help. It bears trying to see how fast things are.
Eric
^ permalink raw reply
* Re: ax25 support in aprsd
From: Hamish Moffatt @ 2004-01-26 7:07 UTC (permalink / raw)
To: linux-hams
In-Reply-To: <Pine.LNX.4.44.0401260023590.3685-100000@mobile.adis.ca>
On Mon, Jan 26, 2004 at 12:25:42AM -0600, Adi Linden wrote:
> I am trying to get aprsd to work with ax25 support. But documentations
> seems to be non existant. Any pointers on how to do it?
Err, there's not much to it. I thought the example configuration file
should be enough. (I wrote the ax.25 code for aprsd.)
Set your tncport to the name of the port from /etc/ax25/axports.
Set aprspath to "APRS v WIDE" or similar.
Make sure AX.25 is recognised at compile time, which looks for the
include files in /usr/include.
That's all there is to it.
Which aprsd version are you using?
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
^ permalink raw reply
* Re: [PATCH] sungem: add support for G5 PowerMac, some PM fixes
From: David S. Miller @ 2004-01-26 7:01 UTC (permalink / raw)
To: benh; +Cc: jgarzik, linux-kernel
In-Reply-To: <1074813192.949.121.camel@gaston>
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: Fri, 23 Jan 2004 10:13:12 +1100
Anyway, here's the fixed version.
Applied, thanks. This one might have to wait for 2.6.3-pre1 though
for merging.
The 2.4 backport will come next week hopefully when I'll walk
through all my pending 2.4 stuffs, I want to dbl check a few things
in it first (and I'm not yet 100% certain I will merge the G5
support in 2.4 upstream anyway).
You should be able to literally copy the 2.6.x driver into the 2.4.x
tree with perhaps only a one liner or two (if that).
the new PCI ID isn't yet in Linus tree, but it's in the patches
I'm currently sending to Andrew.
I'd prefer in the future you not do it this way, just give it
instead within the driver update so that you patch by itself
stands alone.
Thanks.
^ permalink raw reply
* Re: Troubles Compiling 2.6.1 on SuSE 9
From: Marco Rebsamen @ 2004-01-26 7:14 UTC (permalink / raw)
To: Christian; +Cc: linux-kernel
In-Reply-To: <401444C6.3090602@g-house.de>
Am Sonntag, 25. Januar 2004 23:35 schrieben Sie:
> Marco Rebsamen wrote:
> | bineo:/usr/src/linux-2.6.1 # LANG=C LC_ALL=C objcopy -O binary -R .note
> | -R .comment -S vmlinux arch/i386/boot/compressed/vmlinux.bin
> | Ungültiger Maschinenbefehl
>
> try with "export LANG=C && objcopy ...." to get english messages.
>
> also: what binutils (objcopy -V), gcc, make, etc.. do you use? have you
> bugged SuSE yet?
>
> Christian.
bineo:/home/mr # rpm -q binutils
binutils-2.14.90.0.5-43
bieno:/home/mr # objcopy -V
GNU objcopy 2.14.90.0.5 20030722 (SuSE Linux)
Copyright 2002 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License. This program has absolutely no warranty.
bineo:/home/mr # gcc -v
Reading specs from /usr/lib/gcc-lib/i586-suse-linux/3.3.1/specs
Konfiguriert mit: ../configure --enable-threads=posix --prefix=/usr
--with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/
man --libdir=/usr/lib --enable-languages=c,c++,f77,objc,java,ada
--disable-checking --enable-libgcj --with-gxx-include-dir=/usr/include/g++
--with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit
i586-suse-linux
Thread model: posix
gcc-Version 3.3.1 (SuSE Linux)
wave-master:/home/mr # make -v
GNU Make 3.80
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
but the rpoblem with objcopy are solved. It was damaged. I reinstalled the
binutils package and it worked. Now i got problems with the modules.
PARTICULAR PURPOSE.
^ permalink raw reply
* Re: [PATCH] sungem: add support for G5 PowerMac, some PM fixes
From: Benjamin Herrenschmidt @ 2004-01-26 7:13 UTC (permalink / raw)
To: David S. Miller; +Cc: Jeff Garzik, Linux Kernel list
In-Reply-To: <20040125.230102.71560587.davem@redhat.com>
On Mon, 2004-01-26 at 18:01, David S. Miller wrote:
> From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Date: Fri, 23 Jan 2004 10:13:12 +1100
>
> Anyway, here's the fixed version.
>
> Applied, thanks. This one might have to wait for 2.6.3-pre1 though
> for merging.
That's fine, the rest of the PowerMac updates are waiting for 2.6.3 too.
> The 2.4 backport will come next week hopefully when I'll walk
> through all my pending 2.4 stuffs, I want to dbl check a few things
> in it first (and I'm not yet 100% certain I will merge the G5
> support in 2.4 upstream anyway).
>
> You should be able to literally copy the 2.6.x driver into the 2.4.x
> tree with perhaps only a one liner or two (if that).
Yes. I'll do that along with other things I need to backport.
> the new PCI ID isn't yet in Linus tree, but it's in the patches
> I'm currently sending to Andrew.
>
> I'd prefer in the future you not do it this way, just give it
> instead within the driver update so that you patch by itself
> stands alone.
Ok.
Ben.
^ permalink raw reply
* Re: ax25 support in aprsd
From: Adi Linden @ 2004-01-26 7:19 UTC (permalink / raw)
To: Hamish Moffatt; +Cc: linux-hams
In-Reply-To: <20040126070735.GA20474@cloud.net.au>
> Err, there's not much to it. I thought the example configuration file
> should be enough. (I wrote the ax.25 code for aprsd.)
Wow! That's easy but I really didn't get it from the example config.
> Set your tncport to the name of the port from /etc/ax25/axports.
> Set aprspath to "APRS v WIDE" or similar.
What does the aprspath do? I don't quite understand the APRS v WIDE, but
that could be because I should really be sleeping.
> Make sure AX.25 is recognised at compile time, which looks for the
> include files in /usr/include.
Got that.
> Which aprsd version are you using?
I build aprsd-2.2.5-15 from sourceforge successfully with ax25 support. I
tried aprsd215b9 with the DL5DI patch but it wasn't as successful. Any
opinion on which one to choose?
Thanks!
Adi
^ permalink raw reply
* Re: sched-idle and disk-priorities for 2.6.X
From: Pavel Machek @ 2004-01-26 7:19 UTC (permalink / raw)
To: Bill Davidsen; +Cc: Rik van Riel, Valdis.Kletnieks, kernel list
In-Reply-To: <40147637.20806@tmr.com>
Hi!
> >>Is there effective way to limit RSS?
> >
> >
> >Want me to port the RSS stuff from 2.4-rmap to 2.6 ?
>
> What's the effort? It's useful for programs which use a lot of memory,
> particularly for those which only do it on some data sets. It would
> certainly act as a safty net.
If you have two apps which oth need lots of memory, and want to
"renice" one to run slower.
Alternatively when you have one app eating a lots of memory and you
want your system to remain usable.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
^ permalink raw reply
* Re: [ANNOUNCE] Cooperative Linux
From: Dan Aloni @ 2004-01-26 7:23 UTC (permalink / raw)
To: Karim Yaghmour; +Cc: Nuno Silva, Linux Kernel List
In-Reply-To: <40149F25.1040209@opersys.com>
On Mon, Jan 26, 2004 at 12:01:25AM -0500, Karim Yaghmour wrote:
>
> Dan Aloni wrote:
> >I can't say exactly when, but several people volunteered to work on this.
>
> BTW, I've been looking at the code. Many of the tricks done for forcing
> NT to share resources with Linux should be unnecessary for a Linux setup.
> Also, the code apparently assumes only two OSes. You probably want to
> check the detailed discussion I had written some time ago about how to
> easily obtain an SMP cluster with Linux (N instances on separate CPUs
> with very few code modifications required):
> http://www.opersys.com/adeos/dox/practical-smp-clusters/practical-smp-clusters.html
> Some of the code you've already written can be used as-is to this end.
> The nanokernel side still needs some extending, but you've brought things
> one step closer to completion.
The code doesn't assume two OS's. It only assumes that the VM monitor
switches between the host OS and the guest OS alone, but that doesn't
prevent you from running two or more monitors, which would be scheduled
by the host OS scheduler.
> On a UP system, instead of running just 2 instances, you can load a
> nanokernel in a fixed RAM region and remap it in every instance's
> virtual memory. You can then use a slightly modified kexec to start
> independent images in different RAM regions. I had discussed this
> with Eric at the last OLS and he was interested. The added
> advantage with Adeos is that you could then share a single interrupt
> pipeline among all OSes, and have different OSes manage different hardware
> components. Of course, if you add the PCI allocation code I cover in the
> above paper, you can then have things like two kernels independently
> managing, for example, two seperate sets of ethernet card and SCSI disk.
> There's some pretty cool stuff to be done here, away from the simple
> virtual devices. You could also have a virtual ethernet layer which is
> shared by all OS images, and then have a private network between all
> OS instances. With Adeos, you can also have one kernel take care of
> all hard-rt operations and another kernel take care of the soft-rt
> operations. All of it is fairly hardware independent.
That's interesting, but allowing Cooperative Linux to directly access
the hardware is problematic on systems like Windows. coLinux's goal is
more focused on bringing Linux to other operating systems than resources
sharing among several operating systems.
However, I have no doubt it can be used to run several virtual Linux's
on a single SMP Linux machine, with emphasis on the 'virtual'.
--
Dan Aloni
da-x@gmx.net
^ permalink raw reply
* Re: MPC823E SMC/I2C/SPI micropatch
From: Jan Damborsky @ 2004-01-26 7:23 UTC (permalink / raw)
To: Steven Blakeslee, linuxppc-dev
In-Reply-To: <D73A25AA6E54D511AD74009027B1110F5BB008@ORION>
Hi,
I have found out that CPM micropatch
available in linux-2.4 from Wolfgang Denk
site (the kernel we use successfuly on our
custom boards at present) is applicable as well.
After some changes in 8xx CPM and UART code
I have succeeded.
For now, ethernets on SCC2 and SCC3, UARTs
on SMC1 and SMC2 work altogether.
Thank you very much.
Sincerely, Jan Damborsky
Steven Blakeslee wrote:
> I've used the one in the linuxppc_2_4_devel tree with success.
> http://ppc.bkbits.net
> It is found in directory arch/ppc/8xx_io
>
> -----Original Message-----
> From: Jan Damborsky [mailto:jan.damborsky@devcom.cz]
> Sent: Monday, January 19, 2004 11:20 AM
> To: linuxppc-dev@lists.linuxppc.org
> Subject: MPC823E SMC/I2C/SPI micropatch
>
>
>
> Hi,
>
> we want to use SCCs and SMCs on our custom board
> with MPC823E in following configuration:
> Ethernets on SCC2 and SCC3,
> UARTs on SMC2 and SMC1. Normally it is not possible,
> because SCC3 ethernet parameter RAM overlaps SMC1 one.
> I have found Motorola micropatch
> for SMC/I2C/SPI relocation only for MPC850 and MPC860
> processors. They are slightly different (exactly
> these patches differ in one word). I would like
> to ask if somebody tries to use one of them
> for MPC823E. Or if another microcode patch exists
> especially for MPC823E.
>
> Regards, Jan Damborsky
>
>
>
>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply
* Re: WP 5.1, graphical preview, in console
From: Rob Ristroph @ 2004-01-26 7:29 UTC (permalink / raw)
To: linux-msdos
In-Reply-To: <Pine.LNX.4.44.0401260144330.9192-100000@solarflow.dyndns.org>
>>>>> "Justin" == Justin Zygmont <jzygmont@solarflow.dyndns.org> writes:
Justin>
Justin> On 25 Jan 2004, Rob Ristroph wrote:
>> >>>>> "Justin" == Justin Zygmont <jzygmont@solarflow.dyndns.org> writes:
Justin>
Justin> did you set your $_console=1 and $_graphics=1 in dosemu.conf?
>>
>> Yes. Actually it is conf/dosemurc in the precompiled distribution. I
>> also set $_video = "vga", $_rawkeyboard = (1), $_vbios_post = (1),
>> $_chipset = "ati" and also tried $_chipset = "plainvga", and various
>> combinations of those.
>>
>> Does graphics from the console work for you ? Are you using the
>> binary distribution, or did you compile it from source ? If so, did
>> you edit compiletime-settings at all ?
Justin>
Justin> not sure about wp 5.1 but console graphics work for most
Justin> programs for me. I compiled my own, but I don't see why that
Justin> should really matter. I have a custom download you can try if
Justin> you want to see: ftp://solarflow.dyndns.org How about xdosemu?
Justin> if that won't do the graphics, I don't know what will.
I can do everything in xdosemu; but I explicitly want to get it
working in console mode. This isn't just because of some whim, the
computer that will use this has a very small monitor and X sucks on
it.
I downloaded your package (thanks for letting me try that) and it
didn't do graphics in X or console. (I had to edit a script because
it appeared to be set to run as root). I think my next step will be
to compile everything as you did and see if I can get it working.
--Rob
^ permalink raw reply
* Re: Q: Filesystem choice..
From: David Woodhouse @ 2004-01-26 7:40 UTC (permalink / raw)
To: Eric W. Biederman; +Cc: linux-mtd
In-Reply-To: <m3bror89u9.fsf@maxwell.lnxi.com>
On Mon, 2004-01-26 at 00:09 -0700, Eric W. Biederman wrote:
> Has anyone gotten as far as a proof. Or are there some informal
> things that almost make up a proof, so I could get a feel? Reserving
> more than a single erase block is going to be hard to swallow for such
> a small filesystem.
You need to have enough space to let garbage collection make progress.
Which means it has to be able to GC a whole erase block into space
elsewhere, then erase it. That's basically one block you require.
Except you have to account for write errors or power cycles during a GC
write, wasting some of your free space. You have to account for the
possibility that what started off as a single 4KiB node in the original
block now hits the end of the new erase block and is split between that
and the start of another, so effectively it grew because it has an extra
node header now. And of course when you do that you get worse
compression ratios too, since 2KiB blocks compress less effectively than
4KiB blocks do.
When you get down to the kind of sizes you're talking about, I suspect
we need to be thinking in bytes rather than blocks -- because there
isn't just one threshold; there's many, of which three are particularly
relevant:
/* Deletion should almost _always_ be allowed. We're fairly
buggered once we stop allowing people to delete stuff
because there's not enough free space... */
c->resv_blocks_deletion = 2;
/* Be conservative about how much space we need before we allow writes.
On top of that which is required for deletia, require an extra 2%
of the medium to be available, for overhead caused by nodes being
split across blocks, etc. */
size = c->flash_size / 50; /* 2% of flash size */
size += c->nr_blocks * 100; /* And 100 bytes per eraseblock */
size += c->sector_size - 1; /* ... and round up */
c->resv_blocks_write = c->resv_blocks_deletion + (size / c->sector_size);
/* When do we allow garbage collection to merge nodes to make
long-term progress at the expense of short-term space exhaustion? */
c->resv_blocks_gcmerge = c->resv_blocks_deletion + 1;
You want resv_blocks_write to be larger than resv_blocks_deletion, and I
suspect you could get away with values of 2 and 1.5 respectively, if we
were counting bytes rather than whole eraseblocks.
Then resv_blocks_gcmerge wants to be probably about the same as
resv_blocks_deletion, to make sure we get as much benefit from GC as
possible.
> > > And I don't know if yaffs or yaffs2 is any better.
> >
> > They're for NAND, not NOR flash.
>
> I think I have heard about a port to NOR flash, but tuned
> for NAND flash I would be really surprised if they were different.
>
> > > In addition boot time is important so it would be ideal if I did not
> > > to read every byte of the ROM chip to initialize the filesystem.
> >
> > There have been efforts to improve JFFS2 performance in this respect. It
> > still reads the _header_ from each node of the file system, but doesn't
> > actually checksum every node any more.
>
> That should help. It bears trying to see how fast things are.
>
> Eric
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
--
dwmw2
^ permalink raw reply
* Re: chrp mmu and booting.
From: Segher Boessenkool @ 2004-01-26 7:51 UTC (permalink / raw)
To: Benjamin Herrenschmidt; +Cc: linuxppc-dev list, Peter Bergner, Sven Luther
In-Reply-To: <1074906498.1262.52.camel@gaston>
> If you are talking about non-IBM HW, then you can't rely on what
> happens
> on IBM CHRP as a reference :) Any OF implementation does things
> differently
> (and for example, Apple's one runs in virtual mode, not in real mode,
> thus
> the translate call is useful in case you are loaded at a non-1:1
> address).
Any compliant PowerPC OF implementation is required to be able to run in
both real- and virtual mode. Apple's OF runs in virtual mode by
default;
IBM's in real mode. And neither runs very well in the "other" mode, as
it
is seldom (if ever) tested...
Segher
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply
* Re: chrp mmu and booting.
From: Segher Boessenkool @ 2004-01-26 7:52 UTC (permalink / raw)
To: Peter Bergner; +Cc: linuxppc-dev list, Sven Luther
In-Reply-To: <1074890984.2840.25.camel@otta.rchland.ibm.com>
> Yes, you can boot any 32-bit ELF binary from OF. Yaboot and the zImage
> wrapper for the 64-bit kernel are both 32-bit ELF binaries, so you can
> boot either of these. Note that you cannot boot a plain PPC64 vmlinux,
> as the OF ELF loader doesn't support 64-bit ELF binaries.
This is OF implementation dependent -- for example, the Apple one will
load 64-bit ELF just fine (iirc).
Segher
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.