Linux-Development-Sys Digest #689
Linux-Development-Sys Digest #689, Volume #8 Fri, 4 May 01 04:13:14 EDT Contents: Re: IO system throughput (Greg Copeland) Re: Is linux kernel preemptive?? (Greg Copeland) Re: IO system throughput ([EMAIL PROTECTED]) programming the serial port (Javier Loureiro Varela) Re: Cannot get PHP 4 to compile for my system (Bjorn Pearson) Re: About jiffies in Kernel (=?iso-8859-1?Q?Andr=E9?= David) Re: Interprocess Communication...help (Eric P. McCoy) Re: Cannot load shared object file (Martin) Re: how to register a pci device? Re: About jiffies in Kernel Re: Transfer data to mySQL Server (Frank Ranner) Test (Mulder H.) STLport 4.0 g++ 2.96 (Steve Connet) Hot plug PCI device (Mulder) Re: Is linux kernel preemptive?? (Rik van Riel) Re: Startup service (D. Stimits) Re: Hot plug PCI device (D. Stimits) Re: STLport 4.0 g++ 2.96 (D. Stimits) Re: malloc Bug? (Torsten Blank) Subject: Re: IO system throughput From: Greg Copeland [EMAIL PROTECTED] Date: 03 May 2001 11:17:28 -0500 It's important to remember that the implementation requires kernel support. This is the only way it can dispatch on the number and type of events that it can. Think of this as being a hybrid approach much in the same way that threads often require both kernel and user space support. Greg [EMAIL PROTECTED] writes: Greg Copeland [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] writes: [snip] What do you think of the following system call that exists under FreeBSD and allows to do the thing you like, if i don't err: int kqueue(void) Ya, I read an article about this a number of months back. I think it's pretty cool. From that I've *read*, it is doing exactly what I've been talking about. My memory is a little fuzzy on this, but I think a similar project is underway for Linux. I don't remember if it was being built on the kqueue system or not. Sorry. As for how well the above implementation works, I honestly don't know, but from what I've read, they've done an excellent job. From what i have read also in FreeBSD mailing lists, this mechanisms allows very good performance in some cases. Note that forking a new process is extremely fast on Linux, more than in FreeBSD, so that this mechanism is perhaps not as useful as in FreeBSD. -- Greg Copeland, Principal Consultant Copeland Computer Consulting -- PGP/GPG Key at http://www.keyserver.net DE5E 6F1D 0B51 6758 A5D7 7DFE D785 A386 BD11 4FCD -- -- Michel Talon -- Greg Copeland, Principal Consultant Copeland Computer Consulting == PGP/GPG Key at http://www.keyserver.net DE5E 6F1D 0B51 6758 A5D7 7DFE D785 A386 BD11 4FCD == -- Subject: Re: Is linux kernel preemptive?? From: Greg Copeland [EMAIL PROTECTED] Date: 03 May 2001 11:35:53 -0500 Thanks. That's been my point. Please clarify why you think that interrupt handlers do not count as system calls. Let's review this. Both reside within the kernel. Both are functions. Both are called to service a specific level of functionality. The only distinction is that one is invoked directly by an asynchronous interrupt handler while the other is a synchronous call. Hardly worth making the distinction unless you are getting into a microscopic conversation, which I have pointed out that I was specifically trying to avoid. Now then, since I feel sure that we can agree on the above, adding this level of detail to a high level conversation, I would submit, offers no additional value. Keep in mind, interrupt handlers can and do call other system calls. In essence, when you say an interrupt handler, you are really describing an asynchronous entry point to a system call. In the original conversation, the fact that something was being called asynchronously was specifically deemed, by me, as irrelevant because the level of detail at that point in time could not make any meaningful distinction as to it exact behavior to make mention worthy. The use of system call is a very ambiguous term which I feel people often assign specific attributes that does not really exist. I like to avoid all of that and think of system calls as just that. A function residing within the system. In this case, I think of system as being the kernel. I find that for the vast majority of conversations, the concept holds true and greatly simplifies the thread as far fewer assumptions are needed by the participants. Hope this helps. Thanks, Greg [EMAIL PROTECTED] (Neal Tucker) writes: Greg Copeland [EMAIL PROTECTED] wrote: Kasper Dupont [EMAIL PROTECTED] writes: A system call cannot preempt another system call, no matter what the system looks like
Linux-Development-Sys Digest #689
Linux-Development-Sys Digest #689, Volume #7 Mon, 20 Mar 00 02:13:14 EST
Contents:
Re: GNU C compiler source code (Andy Guibert)
Re: tricky code in super.c (Andy Guibert)
Re: GNU C compiler source code (again... sorry) (Andy Guibert)
Re: To Linyx plhelp help (Andy Guibert)
Re: Bootdisks, rdev, and root filesystems...aargh! (Dances With Crows)
Re: GNU C compiler source code (Andy Guibert)
directory entry reclaim? (Weiguang Shi)
Re: sock_sendmsg() (Dan McGuirk)
Partitionable Devices Rubini (Mark McDougall)
User process virtual memory layout (Sean R. Manning)
Re: how to write/read sector to hd? (Pete Cavender)
Re: Xserver problem (Mario Klebsch)
Re: User process virtual memory layout ("Arthur H. Gold")
Re: User process virtual memory layout (Sean R. Manning)
From: Andy Guibert [EMAIL PROTECTED]
Subject: Re: GNU C compiler source code
Date: Sun, 19 Mar 2000 18:34:10 -0500
Qui Nguyen wrote:
Hi all,
I want to know whether GNU C compiler source code is free or not. If
it's free
where I can download it.
Thanks in advance
I've yet to see GNU software that isn't GPL'ed.
I usually download gcc from the Linux Kernel archives:
http://www.kernel.org/pub/linux/devel/gcc/
--
=
Remove the "nojunk" from my addy when responding.
"May the source be with you, Luke."
--
From: Andy Guibert [EMAIL PROTECTED]
Subject: Re: tricky code in super.c
Date: Sun, 19 Mar 2000 18:38:34 -0500
Weiguang Shi wrote:
I am reading the code of /usr/src/linux/fs/super.c of version 2.0.38.
At line 443, there is "s = 0+super_blocks;". I don't know why this is the
way it is. Would a simple "s=super_blocks;" hurt?
Though it does make the code look cleaner, I do not think that it affects the
compiled binary. If I'm not mistaken, gcc is an optimizing compiler and takes
out inefficiencies such as this one.
--
=
Remove the "nojunk" from my addy when responding.
"May the source be with you, Luke."
--
From: Andy Guibert [EMAIL PROTECTED]
Subject: Re: GNU C compiler source code (again... sorry)
Date: Sun, 19 Mar 2000 18:55:39 -0500
You can also get GCC directly from the GNU ftp site.
ftp.gnu.org
Andy
=
Remove the "nojunk" from my addy when responding.
"May the source be with you, Luke."
--
From: Andy Guibert [EMAIL PROTECTED]
Subject: Re: To Linyx plhelp help
Date: Sun, 19 Mar 2000 19:06:14 -0500
"Bass¨Ð¦õªv" wrote:
can I do this between "iMac (and other's apple ¾÷) " and "linux" ???
How can I do this ???
You're looking for something called Appletalk DDP. It's support can be
compiled into the kernel.
Scope out http://www.eats.com/linux_mac_win/file_services.html for
details.
=
Remove the "nojunk" from my addy when responding.
"May the source be with you, Luke."
--
From: [EMAIL PROTECTED] (Dances With Crows)
Crossposted-To: alt.os.linux,comp.os.linux.misc
Subject: Re: Bootdisks, rdev, and root filesystems...aargh!
Date: 19 Mar 2000 19:06:24 EST
Reply-To: [EMAIL PROTECTED]
On 19 Mar 2000 22:09:20 GMT, Dennis Heltzel
01bf91f0$c15ded00$790a1aac@server shouted forth into the ether:
You need to use a bootmanager like lilo or syslinux to uncompress the root
FS into a RAM
disk and then load the kernel into memory. I've used syslinux for this
quite successfully
Sorry... While lilo or syslinux might make working with RAMdisks a bit
easier, there's no pressing need to use it. All is explained in the
Bootdisk-HOWTO:
http://www.linuxdoc.org/HOWTO/Bootdisk-HOWTO.html
(Besides, being able to mutter weird-looking rdev incantations has more
Hack Value, y'know!)
--
Matt G / Dances With Crows \###| Programmers are playwrights
There is no Darkness in Eternity \##| Computers are lousy actors
But only Light too dim for us to see \#| Lusers are vicious drama critics
(Unless, of course, you're working with NT)\| BOFHen burn down theatres.
--
From: Andy Guibert [EMAIL PROTECTED]
Subject: Re: GNU C compiler source code
Date: Sun, 19 Mar 2000 19:18:04 -0500
Qui Nguyen wrote:
Hi all,
I want to know whether GNU C compiler source code is free or not. If
it's free
where I can download it.
Have you tried ftp.gnu.org? :)
=
Remove the "nojunk" from my addy when responding.
"May the source be with you, Luke."
--
From: Weiguang Shi [EMAIL PROTECTED]
Subject: directory entry reclaim?
Date: Sun, 19 Mar 2000 17
Linux-Development-Sys Digest #689
Linux-Development-Sys Digest #689, Volume #6 Sat, 8 May 99 02:16:36 EDT
Contents:
Re: egcs Warning while building gcc-2.8.1 cross compiler (Johan Kullstam)
Re: Destructive Erase? ("Stefan Monnier "
[EMAIL PROTECTED])
Re: any video camera? ([EMAIL PROTECTED])
Need help. My kernel won't compile on my new system. (Captain Panic)
Re: Mount multi-track CD ROMs? (Igor Zlatkovic)
RPC Brokers ("Thomas J. Clancy")
Re: Change from gcc to egcs gives seg fault in make (Graffiti)
Re: Any program can generate Gif or Jpg chart?
(dovelet2) (Christopher Mahmood)
Re: egcs Warning while building gcc-2.8.1 cross compiler (Dirk Foersterling)
gcc, egcc and compiling glibc2.1 (Vladimir Stanishev)
DMA from hard drive file, or HD file access from kernal. ([EMAIL PROTECTED])
Re: [ANN] CodeWarrior for Red Hat Linux, GNU ed. Shipping ([EMAIL PROTECTED])
Re: [ANN] CodeWarrior for Red Hat Linux, GNU ed. Shipping ([EMAIL PROTECTED])
Re: Glibc rant ("G. Sumner Hayes")
Re: ISDN PCI Cards with Linux other bits (Hans Dumbrajs)
From: Johan Kullstam [EMAIL PROTECTED]
Subject: Re: egcs Warning while building gcc-2.8.1 cross compiler
Date: 07 May 1999 12:57:17 -0400
[EMAIL PROTECTED] (Tom Daley) writes:
I am having problems compiling gcc-2.8.1 as a cross compiler
using egc-1.1.1. I have two systems, one at work and one at home.
My home system has been running Linux for a long time (since 0.99p12).
The system at work I installed last year when I started working
there.
the gcc spec file format changed somewhere between gcc-2.7.2.3 and
egcs-1.0. look in /usr/lib/gcc-lib/???/???/specs (where ??? are the
target and compiler version specific directories.) i had trouble last
year when i wanted to keep gcc 2.7.2.3 and egcs 1.0 around and share
the compilers through the /usr/bin/gcc wrapper and -V and -b options.
i never got it to work due to incompatibilities in the spec file
formats.
On both systems I have built/installed glibc-2.0.7pre6 and egcs-1.1.1.
Then I built gcc-2.8.1 as a cross compiler on the system at work and
all was well. When I try to build the cross compiler at home I get
an error in the build.
why not build egcs as a cross compiler? that way you wouldn't have
the spec file trouble. i use the 2.2.x line of kernels, thus i only
have egcs (now 1.1.2) on my system.
gcc -DCROSS_COMPILE -DIN_GCC-g -DHAVE_CONFIG_H-I. -I.. -I../config \
-DSTANDARD_STARTFILE_PREFIX=\"/usr/local/lib/\"
-DSTANDARD_EXEC_PREFIX=\"/usr/local/lib/gcc-lib/\" -DDEFAULT_TARGET_VERSION=\"2.8.1\"
-DDEFAULT_TARGET_MACHINE=\"i386-wrs-vxworks\" -DTOOLDIR_BASE_PREFIX=\"/usr/local/\" \
-DLANG_SPECIFIC_DRIVER \
-c g++.c
gcc: Warning: use of obsolete %[ operator in specs
see this is what you get. the spec file is different. annoying huh?
you can build the gcc cross compiler in a different --prefix area (say
/usr/local) but then you need to play path games instead of -b/-V
options to gcc.
hope this helps.
--
johan kullstam
--
From: "Stefan Monnier [EMAIL PROTECTED]"
[EMAIL PROTECTED]
Subject: Re: Destructive Erase?
Date: 07 May 1999 13:48:34 -0400
"matthew" == matthew gauthier [EMAIL PROTECTED] writes:
I'm trying to implement a destructive file erase, however, I'm at a
Why bother ?
Stefan "quite serious about it"
--
From: [EMAIL PROTECTED]
Subject: Re: any video camera?
Date: Fri, 07 May 1999 23:01:10 GMT
I would like to know if there are _any_ video camera drivers available (so I
can decide which ones to choose from before I buy). In particular -- what
about the "Big Picture" camera sold by 3com? Is there a driver for that?
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] wrote:
Does anyone know what this is, or what drivers I might
use for it?
Rich.
--
[EMAIL PROTECTED] BiblioTech http://www.postmaster.co.uk/
+44 171 384 6917 Unit 2 Piper Centre Premier European email service
http://www.annexia.org 50 Carnwath RoadOriginal message content
London Copyright © 1999 Richard Jones
= Posted via Deja News, The Discussion Network
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
--
From: Captain Panic [EMAIL PROTECTED]
Subject: Need help. My kernel won't compile on my new system.
Date: 7 May 1999 20:32:35 GMT
I just install RedhAt 6.0 on my system. And it looks good, but I can't
get my kernel to compile with the included egcs 1.1.2 . Here is the
error. Any help would be greatly appreciated. Here is the error:
fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2 -
malign-jumps=2 -malign-functions=2 -DCPU=68
