Re: Linux 2.2.18pre21

Re: Linux 2.2.18pre21

[willy tarreau]

> I don't like to call it BONDING.
> "Bonding" is something where two (or more) channels
> carry data in between two participating systems.
> Like Multilink-PPP, and ISDN Channel Bonding.  Often
> indeed data goes out somehow inter-leaved on the
> physical links.  (Like ISDN Channel Bonding supplies
> a transparent 128 kbps link instead of two 64
> kbps links to the upper layers.)

this is *EXACTLY* what the old bonding driver does,
and what the new one does by default.

> EtherChannel does select the link (out of the group)
> by forming XOR of source and destination MAC
> addresses (their lowest bytes),
.../...
> This gives improved throughput on congested links
> in between two switches, or major server and core
> switches, while preserving data order over the
links.

OK, I've read about it because Thomas Davis asked me
if I would implement it. I didn't find it usefull for
the case of a Linux server directly connected to a
router or a level X switch (x>2) because in this case
only one link is getting used. Perhaps I'm wrong, but
I think this is the major use of the current Linux
bonding driver. However, the new driver is now ready
for such an implementation.

> Blind bonding-type "throw packets on links 0 and 1"
> MAY end up sending ethernet frames out of sequence,
> which for a few LAN based protocols is a great
source
> of upset.
probably, but do you have examples in mind ? if so, I
would add XOR to a next release, but I don't want to
add too much at a time. I consider this release
primarily as a bugfix (smp, security, oopses...), and
as an improvement which now supports link fail-over,
which is also a primary concern when implementing
multilinks.

> Beowulf systems have "bonding" in use for parallel
> Ethernet links in between two machines, however THAT
> is not EtherChannel compatible thing!

yes it is compatible ! compatible doesn't mean it does
not work the same way, but it works with. Both the
cisco and linux drivers agree to receive on each of
their trunk ports, so the difference only resides in
link optimization when sending frames.

> /Matti Aarnio

Willy


___________________________________________________________
Do You Yahoo!? -- Pour dialoguer en direct avec vos amis, 
Yahoo! Messenger : http://fr.messenger.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

compiling 2.4.0-test10 kernel

[Corisen]

hi,

i'm currently running RH7, with 2.2.16-22 kernel, gcc 2.96 on a Sharp Actius
250 notebook.

i've manged to successfully compile 2.4.0-test10 kernel. however, upon
startup there are some failed/error messages:
1. finding module dependencies: depmod *** Unresolved symbols in
/lib/modules/2.4.0-test10/kernel/arch/i386/kernel/apm.o
2. Starting NFS lockd: lockdsvc: Invalid argument [FAILED]

during shutdown, the following failed messages was noticed:
1. Turning off accounting: aacton: Function not implemented
2. Shutting down NFS lockd [FAILED]

the system is also not able to shutdown/power off completely after
"shutdown -h now". however, using RH7 2.2.16 kernel, the notebook was able
to power off. how can i configure it to turn off automatically?

pls kindly advise where i have gone wrong and how to rectify the above
errors.

pls pardon my ignorance as i'm quite new to linux and this is my first
kernel compilation attempt.

thank you very much.

ps: i've tried the kernel compilation on a HP Vectra PII PC and the error
messages are similar.




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

Re: compiling 2.4.0-test10 kernel

[Georg Nikodym]

>>>>> "C" == Corisen  <csyap@starnet.gov.sg> writes:

 C> hi, i'm currently running RH7, with 2.2.16-22 kernel, gcc 2.96 on
 C> a Sharp Actius 250 notebook.

 C> i've manged to successfully compile 2.4.0-test10 kernel. however,
 C> upon startup there are some failed/error messages:
 C> 1. finding module dependencies: depmod *** Unresolved symbols in
 C> /lib/modules/2.4.0-test10/kernel/arch/i386/kernel/apm.o

There are two things you can do about this:

 1. Disable module versioning.
 2. Copy the System.map file that's made during the kernel build to
    /boot/System.map-2.4.0-test10.

Personally, I do 2.  Though, now I'm attempting to get the maestro
driver working again and this is getting in my way.  So my question to
those that know more is what is the correct way to build a module such
that it'll insmod in the face of module versioning.  Is this something
for the FAQ?

 C> 2. Starting NFS lockd: lockdsvc: Invalid argument [FAILED]

I've been ignoring this (I'm sure at my peril).

 C> during shutdown, the following failed messages was noticed:
 C> 1. Turning off accounting: aacton: Function not implemented

You can try enabling BSD process accounting in your configuration.  I
have not and also get this message (and don't care).

 C> 2. Shutting down NFS lockd [FAILED]

As above.

 C> the system is also not able to shutdown/power off completely after
 C> "shutdown -h now". however, using RH7 2.2.16 kernel, the notebook
 C> was able to power off. how can i configure it to turn off
 C> automatically?

My laptop (a Fujitsu E6520 stop powering off with RH7 regardless of
whether I used the supplied kernel or the test10 that I built), so
consider yourself lucky ;-)

Also, the default compiler on RH7 is not correct.  Use kgcc instead
(ie. make CC=kgcc bzImage).  The gcc2.96 is said/known not to work for
kernel work.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: compiling 2.4.0-test10 kernel

[Keith Owens]

On Fri, 10 Nov 2000 11:23:29 -0500 (EST), 
"Georg Nikodym" <georgn@somanetworks.com> wrote:
> C> i've manged to successfully compile 2.4.0-test10 kernel. however,
> C> upon startup there are some failed/error messages:
> C> 1. finding module dependencies: depmod *** Unresolved symbols in
> C> /lib/modules/2.4.0-test10/kernel/arch/i386/kernel/apm.o
>
>There are two things you can do about this:
>
> 1. Disable module versioning.
> 2. Copy the System.map file that's made during the kernel build to
>    /boot/System.map-2.4.0-test10.

System.map has nothing, repeat nothing to do with depmod at startup.
Yes, you can run depmod reading from a System.map but that only makes
sense before you boot the new kernel.  Once you have booted your
new kernel, depmod -a reads from kernel memory, not System.map.

>those that know more is what is the correct way to build a module such
>that it'll insmod in the face of module versioning.  Is this something
>for the FAQ?

Current Makefiles sometimes break with module versioning, the design is
inherently wrong but rewriting the entire Makefile system just before
the release of Linux 2.4 is not an option.  This should be in the FAQ,
Richard, please add.

Q.  Why do I get unresolved symbols like foo__ver_foo in modules?

A.  If /proc/ksyms or the output from depmod -ae contains symbols like
    "foo__ver_foo" then you have been bitten by the broken Makefile
    code for symbol versioning.  The only safe way to recover is save
    your config, delete everything, restore the config and recompile.

     mv .config ..
     make mrproper
     mv ../.config .
     make oldconfig
     make dep clean bzImage modules
     install, boot

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

Re: compiling 2.4.0-test10 kernel

[Georg Nikodym]

>>>>> "KO" == Keith Owens <kaos@ocs.com.au> writes:

 KO> On Fri, 10 Nov 2000 11:23:29 -0500 (EST), "Georg Nikodym"
 KO> <georgn@somanetworks.com> wrote:
 C> i've manged to successfully compile 2.4.0-test10 kernel. however,
 C> upon startup there are some failed/error messages:
 C> 1. finding module dependencies: depmod *** Unresolved symbols in
 C> /lib/modules/2.4.0-test10/kernel/arch/i386/kernel/apm.o
 >>
 >> There are two things you can do about this:
 >>
 >> 1. Disable module versioning.
 >> 2. Copy the System.map file that's made during the kernel build to
 >> /boot/System.map-2.4.0-test10.

 KO> System.map has nothing, repeat nothing to do with depmod at
 KO> startup.  Yes, you can run depmod reading from a System.map but
 KO> that only makes sense before you boot the new kernel.  Once you
 KO> have booted your new kernel, depmod -a reads from kernel memory,
 KO> not System.map.

OK.  Makes sense.  My first kicks at building and running a kernel had
these problems (with module loading) until I added the copying of
System.map to my installation procedure.  I was led to this by
messages in /var/log/messages...  Thanks for the additional pointers.

 KO> Q.  Why do I get unresolved symbols like foo__ver_foo in modules?

 KO> A.  If /proc/ksyms or the output from depmod -ae contains symbols
 KO>     like
 KO> "foo__ver_foo" then you have been bitten by the broken Makefile
 KO> code for symbol versioning.  The only safe way to recover is save
 KO> your config, delete everything, restore the config and recompile.

 KO> mv .config ..  make mrproper mv ../.config .  make oldconfig make
 KO> dep clean bzImage modules install, boot

OK, but I guess my question wasn't very clear.  I have a kernel tree,
I add a printk to maestro.c and make modules.  I cannot load the
module until I rebuild and reinstall everything.  Is there a way to
avoid this headache, or, stated differently:  What's the prescribed
way to be able to load, unload, build, test modules?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: compiling 2.4.0-test10 kernel

[Anton Altaparmakov]

At 18:25 10/11/2000, Georg Nikodym wrote:
>OK, but I guess my question wasn't very clear.  I have a kernel tree,
>I add a printk to maestro.c and make modules.  I cannot load the
>module until I rebuild and reinstall everything.  Is there a way to
>avoid this headache, or, stated differently:  What's the prescribed
>way to be able to load, unload, build, test modules?

I do the following when I am working on the NTFS driver:

1st: make mrproper && make menuconfig && make dep && make bzImage && make 
modules && make modules_install
2nd: install new kernel, lilo, reboot into new kernel
3rd: edit the <mymodule>'s source.
4th: make modules && make modules_install && depmod -a && rmmod <mymodule> 
&& modprobe <mymodule>
5th: do testing I wanted to do.
6th go to 3rd step and repeat until satisfied with result.

[NB. Obviously replacing <mymodule> with the module name of whatever I am 
looking at.
NB. I have put this in a few convenience scripts...]

This procedure works fine, or at least it does so for all modules I have 
tried it with (which isn't many, since I only keep NTFS, md and linear as 
modules...).

HTH,

         Anton

-- 
      "Education is what remains after one has forgotten everything he 
learned in school." - Albert Einstein
-- 
Anton Altaparmakov  Voice: +44-(0)1223-333541(lab) / +44-(0)7712-632205(mobile)
Christ's College    eMail: AntonA@bigfoot.com / aia21@cam.ac.uk
Cambridge CB2 3BU    ICQ: 8561279
United Kingdom       WWW: http://www-stu.christs.cam.ac.uk/~aia21/

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