On Tue, Jan 16, 2001 at 11:04:45AM -0800, Theodore Y. Ts'o wrote:
>
> HJ Lu recently pointed me at a potential locking problem
> try_to_free_inodes(), and when I started proding at it, I found what
> appears to be another set of SMP locking issues in the dcache code.
> (But if that were the case,
Unable to handle kernel NULL pointer dereference at virtual address 0003
c01ccf91
*pde =
Oops: 0002
CPU:0
EIP:0010:[]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010086
eax: ebx: c1490400 ecx: cfdeb000 edx: cfeed13c
esi: cfdeb000 edi: 1e2
On Fri, 12 Jan 2001, Frank de Lange wrote:
[I've cut syslog junk away for clarity -- you could just do `dmesg -s 32768'.]
> before network hang
> ===
[...]
> NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
[...]
> 13 0FF 0F 010 1 01199
[...]
> printing
Chris Jones <[EMAIL PROTECTED]> writes:
[...]
I suspect the problem is related to loading the aic7xxx.o module, but the
relevant messages have scrolled off the top of the screen. I tried setting the
VGA mode to extended to give me 50 lines of output, but even though "lilo -q
-v" shows "
On Tue, Jan 16, 2001 at 02:18:43PM -0500, Chris Mason wrote:
> When you mount the FS it tells you which version it is, please include that
> info as well.
I am rebooting with the patch from you (Chris) in about 30 seconds. This is
the output from reiserfs when booting:
reiserfs: checking transac
On Tuesday, January 16, 2001 07:58:37 PM +0100 Jakob Borg
<[EMAIL PROTECTED]> wrote:
> On Tue, Jan 16, 2001 at 10:36:43AM -0800, Linus Torvalds wrote:
>> > I seem to remember more possibly useful information scrolling by my
>> > screen, but it seems to not have made it to the logs, and I will s
Guys,
> And this is a problem that has plagues all PC operating systems, but has
never
> been a problem on the Macintosh. Why? Because the Mac was designed to
handle
> this problem, but the PC never was.
Quite true on this point.
> The Mac never enumerates its devices like the PC does (no C:
On Tuesday, January 16, 2001 07:38:58 PM +0100 Jakob Borg
<[EMAIL PROTECTED]> wrote:
> Hi again,
>
> It seems the problem occurs every time i start fetchmail... Attached are
> ksymoops output and .config (if i remember this time). If there is
> anything else I can do to help debug this, just t
Does anyone remember the reason why SCSI drives were limited to
15 partitions?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
HJ Lu recently pointed me at a potential locking problem
try_to_free_inodes(), and when I started proding at it, I found what
appears to be another set of SMP locking issues in the dcache code.
(But if that were the case, why aren't we seeing huge numbers of
complaints? So I'm wondering if I'm m
On Tue, Jan 16, 2001 at 10:36:43AM -0800, Linus Torvalds wrote:
> >I seem to remember more possibly useful information scrolling by my screen,
> >but it seems to not have made it to the logs, and I will shut down and fsck
> >the filesystem now...
>
> It really needs the stack-trace to debug this
Mark Hahn wrote:
>
> > mode, but the have the option apm=poweroff in my lilo.conf and with the
>
> apm=power-off. I'm looking at modern kernels, of course (2.4+).
> power_off is a valid alternative. at one time, the magic string
> was smp-power-off.
>
Whoops, I should reread my emails befo
Hi again,
It seems the problem occurs every time i start fetchmail... Attached are
ksymoops output and .config (if i remember this time). If there is anything
else I can do to help debug this, just tell me.
Regards,
--
Jakob Borgmailto:[EMAIL PROTECTED] (personal)
UNIX/networ
In article <[EMAIL PROTECTED]>,
Jakob Borg <[EMAIL PROTECTED]> wrote:
>Hi,
>
>I recently got this in my logs after moving /home to reiserfs. It is a plain
>2.4.1-pre7 SMP system (.config attached).
>
>Jan 16 19:15:02 narayan kernel: journal_begin called without kernel lock held
>Jan 16 19:15:02 n
On 16 Jan 01 at 13:22, Chad Miller wrote:
> On Tue, Jan 16, 2001 at 05:56:34PM +, Petr Vandrovec wrote:
> > What does 'lspci -v' say?
>
> #00:01.0 PCI bridge: VIA Technologies, Inc. VT8371 [KX133 AGP] (prog-if 00 \
> #[Normal decode])
> #Flags: bus master, 66Mhz, medium devsel, laten
Hi Alan,
On 16 Jan 2001, Christoph Rohland wrote:
> Hi Alan,
>
> Here comes a patch for swapfs which has all my fixes against
> -ac9. It does the following:
>
> - Fix IPC_LOCK (also in 2.4.1-pre7) - Do accounting right (Also send
> to Linus) - memparse returns unsigned long long (Also send to L
** Reply to message from Eddie Williams <[EMAIL PROTECTED]> on Tue,
16 Jan 2001 12:24:49 -0500
> That is not totally true. There are two problems here, one is where you have
> different controllers in your system and the other is where you have multiples
> of the same controller. What you li
On Tue, Jan 16, 2001 at 05:56:34PM +, Petr Vandrovec wrote:
> What does 'lspci -v' say?
Hi, Petr.
I'm sorry for the verbosity, all. Here it is:
#00:00.0 Host bridge: VIA Technologies, Inc. VT8371 [KX133] (rev 02)
#Flags: bus master, medium devsel, latency 0
#Memory at d
Hi,
I recently got this in my logs after moving /home to reiserfs. It is a plain
2.4.1-pre7 SMP system (.config attached).
Jan 16 19:15:02 narayan kernel: journal_begin called without kernel lock held
Jan 16 19:15:02 narayan kernel: kernel BUG at journal.c:423!
Jan 16 19:15:02 narayan kernel: CP
Is there something special that linux vendors do to make their machines
power off when they are shutdown? I've used both redhat and mandrake
supplied 2.4.x SMP kernels, and all of them manage to turn off the
machine when I shutdown. I realize that apm is not supported in smp
mode, but the have t
[EMAIL PROTECTED] said:
> [Venkatesh Ramamurthy]
Your name is already in the headers of the mail you sent. There's no need to
repeat it.
> The LILO boot loader and the LILO command line utility should be changed
> for this.
> Is anybody doing this? -
There are patches available for the
Hi Alan,
Here comes a patch for swapfs which has all my fixes against -ac9. It
does the following:
- Fix IPC_LOCK (also in 2.4.1-pre7)
- Do accounting right (Also send to Linus)
- memparse returns unsigned long long (Also send to Linus)
- Fix the unresolved symbols w/o CONFIG_SWAPFS
- Introduce
On Tue, 16 Jan 2001, Ingo Molnar wrote:
>
> yep, correct. But take a look at the trick it does with file descriptors,
> i believe it could be a useful way of doing things. It basically
> privatizes a struct file, without inserting it into the enumerated file
> descriptors. This shows that 'nati
> From a layering point of view, it makes a lot more sense to
> me for the label (or signature or whatever) for this purpose
> to be in the partition table than inside the filesystem. The
> parts of the system that assign devices their identities already
> know about that part of the disk.
Venkatesh Ramamurthy wrote:
>
> Hi,
> I have one issue which requires fix from the linux kernel.
> Initially i put a SCSI controller and install the OS on the drive connected
> to it. After installing the OS (on sda), the customer puts another SCSI
> controller. The BIOS for the first controller
>If we can truly go for label based mounting
>and lilo'ing this would solve the problem.
>From a layering point of view, it makes a lot more sense to
me for the label (or signature or whatever) for this purpose
to be in the partition table than inside the filesystem. The
parts of the system th
On Tue, 16 Jan 2001 16:51:38 GMT, Venkatesh Ramamurthy <[EMAIL PROTECTED]> wrote:
> [Venkatesh Ramamurthy] Just think an end-user fuguring out this
> Asking him to change PCI slots and trying it out. My point is the end user
> should not worry about all this. All he does is plugs a new
> Why does the end-user have to compile the kernel? Most distributions
> provide a kernel with no SCSI drivers in it, but use an initrd to get
> the root SCSI driver in (man mkinitrd on any Redhat box). Just
> distribute all SCSI drivers as modules and you won't have any problems.
>
That is n
"Albert D. Cahalan" <[EMAIL PROTECTED]> writes:
> > 1) top (procps-2.0.7) gives me the messages :
> > 'bad data in /proc/uptime'
> > 'bad data in /proc/loadavg'
> > cat /proc/uptime
> > 1435.30 904.74
> > cat /proc/loadavg
> > 0.01 0.21 0.29 1/17 19444
> > What is wrong ?
You probably have loc
The patch below (against vanilla 2.4.0) makes Linux recognize
PCI-Devices sitting in another PCI bus than 0 (or 1).
This was tested on a Netfinity 7100-8666 using a ServerWorks chipset.
00:00.0 Host bridge: ServerWorks CNB20HE (rev 21)
00:00.1 Host bridge: ServerWorks CNB20HE (rev 01)
00:00.2
Venkatesh Ramamurthy wrote:
>
> > When the cards are of different make the order is solely dependent on
> > the order that the drivers are initialized in the kernel. If you have
> > modules enabled, only build the driver for your root device into the
> > kernel image and have the other modular.
David Woodhouse wrote :
> [EMAIL PROTECTED] said:
> > we need some kind of signature being written in the drive, which the
> > kernel will use for determining the boot drive and later re-order
> > drives, if required.
>
> > Is someone handling this already?
>
> It should be possibl
> Why is this a SCSI ML problem? The problem is that the OS can't figure
> out
> where to mount root from. Sounds like an OS problem.
> I think the file system label is the leading candidate to solve this. One
>
> really does not care if the root disk is called /dev/sda or /dev/fred.
> All
On 15 Jan 01 at 19:22, Chad Miller wrote:
> I worry about some PCI initialization output (from dmesg):
>
> # PCI: Probing PCI hardware
> # Unknown bridge resource 0: assuming transparent
> # PCI: Using IRQ router VIA [1106/0686] at 00:07.0
> # PCI: Cannot allocate resource region 0 of device 01:
> The scsi host numbers will be allocated to the HBAs in
> the order shown starting at 0. This method does not
> distinguish between the two advansys controllers, luckily
> swapping their positions on the PCI bus does.
[Venkatesh Ramamurthy] Just think an end-user fuguring out this
A
Why is this a SCSI ML problem? The problem is that the OS can't figure out
where to mount root from. Sounds like an OS problem.
I think the file system label is the leading candidate to solve this. One
really does not care if the root disk is called /dev/sda or /dev/fred. All
one cares is
Venkatesh Ramamurthy wrote:
>
> Hi,
> I have one issue which requires fix from the linux kernel.
> Initially i put a SCSI controller and install the OS on the drive connected
> to it. After installing the OS (on sda), the customer puts another SCSI
> controller. The BIOS for the first controller
> > Is someone handling this already?
>
> "mount by uuid"?
>
> Amiga's Rigid Disk Block?
[Venkatesh Ramamurthy] Something like this is better. The problem
is where do we store this info. Last sector is one of the options. Does
anyone know where NT stores this info?
-
To unsubscribe
> This is due to the fixed ordering of the scsi drivers. You can change the
> order of the scsi hosts with the "scsihosts" kernel parameter. See
> linux/drivers/scsi/scsi.c
[Venkatesh Ramamurthy] I think it would be a nice idea if we can
make this process automatic , with out user typing
I saw the exact same problem on my Adaptec scsi controller.
I initially solved the problem setting the data transfer rate from
80Mb/s to 40MB/s, but I see that yours is already 40MB/s, so this is not
an option for you.
Later I saw an announcement from Justin T. Gibbs, who, I beleive, is
curre
On Tue, 16 Jan 2001, Venkatesh Ramamurthy wrote:
> we need some kind of signature being written in the drive, which the kernel
> will use for determining the boot drive and later re-order drives, if
> required.
>
> Is someone handling this already?
"mount by uuid"?
Amiga's Rigid Disk Block?
> When the cards are of different make the order is solely dependent on
> the order that the drivers are initialized in the kernel. If you have
> modules enabled, only build the driver for your root device into the
> kernel image and have the other modular. This lets you control the
> initializa
> In article <1355693A51C0D211B55A00105ACCFE64E9518C@ATL_MS1> you wrote:
>
> > we need some kind of signature being written in the drive, which the
> kernel
> > will use for determining the boot drive and later re-order drives, if
> > required.
>
> Like the ext2 labels? (man e2label)
[Ve
Florent Cueto
Java developer
Socks via HTTP Homepage : http://www.javawork.net
(A program to tunnel socks requests via HTTP).
- Original Message -
From: "Venkatesh Ramamurthy" <[EMAIL PROTECTED]>
To: "'David Woodhouse'" <[EMAIL PROTECTED]>; "Venkatesh Ramamurthy"
<[EMAIL PROTECTED]>
Cc:
Venkatesh Ramamurthy wrote:
>
> > It should be possible to read the BIOS setting for this option and
> > behave accordingly. Please give full details of how to read and interpret
> > the information stored in the CMOS for all versions of AMI BIOS, and I'll
> > take a look at this.
> [Venk
The maestro3 driver in ac9 oopses, due to trying to deref an
unitialized pointer. Here's the oops:
ksymoops 2.3.7 on i686 2.4.1-pre7. Options used
-v /boot/vmlinuz (specified)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.1-pre7/ (default)
-m /
In article <1355693A51C0D211B55A00105ACCFE64E9518C@ATL_MS1> you wrote:
> we need some kind of signature being written in the drive, which the kernel
> will use for determining the boot drive and later re-order drives, if
> required.
Like the ext2 labels? (man e2label)
Greetings,
Arjan van de
> It should be possible to read the BIOS setting for this option and
> behave accordingly. Please give full details of how to read and interpret
> the information stored in the CMOS for all versions of AMI BIOS, and I'll
> take a look at this.
[Venkatesh Ramamurthy] When i meant BIOS sett
I've got a 20 drive raid0 set up off of two asus fiber
channel controllers using the qlogicfc.c driver. (I
think it's a variant of ISP2200.) Dual pentium 866
SMP machine, apparently stable under NT. Half a gig
of ram, booting off of a different drive (hanging off
of an LSI1010 scsi controller n
[EMAIL PROTECTED] said:
> we need some kind of signature being written in the drive, which the
> kernel will use for determining the boot drive and later re-order
> drives, if required.
> Is someone handling this already?
It should be possible to read the BIOS setting for this option and
beha
> " " == Mogens Kjaer <[EMAIL PROTECTED]> writes:
>> getdents64(3, /* 6 entries */, 65536) = 160 lseek(3,
>> 1547825467, SEEK_SET) = 1547825467 ... getdents64(3, /* 1
>> entries */, 65536) = 32
BTW: there does in any case seem to be a bug in your version of
glibc. getdents64() i
"Michael D. Crawford" wrote:
> Under 2.4.0-ac4 I find lots of mentions of the Sangoma S514 PCI Multiprotocol
> Wide Area Networking card in
>
> drivers/net/wan/sdla*
>
> But in Documentation/Configure.help under CONFIG_VENDOR_SANGOMA I only see
> mention of the S502E(A), S503 and S508. These sa
Hi all,
I'm writing a driver which uses also kernel_threads
and file operations (/dev and /proc).
I was not able yet to find out why and when to use
[un]lock_kernel()
Can someone please give me a hint where to find some
infos in using lock_kernel() for 2.2 and 2.4.
What exactly is/must be pr
> " " == Mogens Kjaer <[EMAIL PROTECTED]> writes:
> getdents64(3, /* 6 entries */, 65536) = 160
> lseek(3, 1547825467, SEEK_SET) = 1547825467
> ...
> getdents64(3, /* 1 entries */, 65536) = 32
I'll bet it's the lseek that's screwing things up again. IIRC IRIX has
an ex
Hi,
I have one issue which requires fix from the linux kernel.
Initially i put a SCSI controller and install the OS on the drive connected
to it. After installing the OS (on sda), the customer puts another SCSI
controller. The BIOS for the first controller has BIOS enabled and for the
second cont
Jakub Jelinek wrote:
> > This makes me wonder...
> >
> > If the kernel only kept a queue of the three smallest unused fd's, and
> > when the queue emptied handed out whatever it liked, how many things
> > would break? I suspect this would cover a lot of bases...
>
> First it would break Unix98
Hello,
I have a problem using the nfs client in kernel 2.4.0
My server is an SGI running IRIX 6.5.8
This tiny program, t1.c, displays the problem:
#include
#include
main()
{
DIR *dp;
struct dirent *de;
dp=opendir(".");
while((de=readdir(dp))!=NULL)
{
printf("%s\n", de->d_name
"James H. Cloos Jr." wrote:
>
> Michael> Please read and comment! :)
>
> There should be some discussion on what to do about filenames which
> contain colons in such a setup. Moving a file w/ a colon from a fs
> which does not support named streams to one which does should DTRT;
> exactly what
On Tue, Jan 16, 2001 at 10:05:06AM -0500, David L. Parsley wrote:
> Felix von Leitner wrote:
> > > close (0);
> > > close (1);
> > > close (2);
> > > open ("/dev/console", O_RDWR);
> > > dup ();
> > > dup ();
> >
> > So it's not actually part of POSIX, it's just to get around fixing
>
Felix von Leitner wrote:
> > close (0);
> > close (1);
> > close (2);
> > open ("/dev/console", O_RDWR);
> > dup ();
> > dup ();
>
> So it's not actually part of POSIX, it's just to get around fixing
> legacy code? ;-)
This makes me wonder...
If the kernel only kept a queue of the t
Hi there,
I am sending your a bunch(!) of logs I think all cast some light over what
ever is wrong with my brand machine. Since I got it up running, it has
been crashing now and then.
It is an AMD T-Bird 900MHz (running at 100MHz x 9 -- not overclocked or begin
tortured in similar ways), 256MB
Thus spake Ingo Molnar ([EMAIL PROTECTED]):
> if you read my (radical) proposal, the identification is based on a kernel
> pointer and a 256-bit random integer. So non-negative integers are not
> needed. (file-IO system-calls would be modified to detect if 'Unix file
> descriptors' or pointers to
Hi!
> > > TWO observations:
> > > - Given Linux's non-pre-emptability of the kernel i get the feeling that
> > > sendfile could starve other user space programs. Imagine trying to send a
> > > 1Gig file on 10Mbps pipe in one shot.
> >
> > Hehe, try sigkilling process doing that transfer. Last tim
Thus spake Ingo Molnar ([EMAIL PROTECTED]):
> But even user-space code could use 'native files', via the following, safe
> mechanizm:
[something reminiscient of a token from a capability system]
> (this 'fingerprint' mechanizm can be used for any object, not only files.)
One good thing about to
On 16 Jan 2001, Christoph Rohland wrote:
> Here is a patch against 2.4.1-pre7 which
>
> 1) Adds prototype for shmem_lock to mm.h
> 2) Again brings the fixes for the accounting. I still think it
>should be applied.
And of course the prototype should be extern...
Greetings
Chr
Thus spake Jamie Lokier ([EMAIL PROTECTED]):
> You would need to use a new open() flag: O_ANYFD.
> The requirement comes from this like this:
> close (0);
> close (1);
> close (2);
> open ("/dev/console", O_RDWR);
> dup ();
> dup ();
So it's not actually part of POSIX, it's just to g
Hello,
I've got a sendmail 8.1.11 process hanging in D state with 2.2.18.
ps -eo fname,tty,pid,stat,pcpu,nwchan,wchan reveals the following:
PID STAT %CPU WCHAN WIDE-WCHAN-COLUMN COMMAND
16176 D 0.0 1f4c28 down_failed sendmail: startup with ...
Is this likely a bug in the kerne
Ingo Molnar wrote:
> struct native_file {
> unsigned long master_fingerprint[8];
> unsigned long file_fingerprint[8];
> struct file file;
> };
>
> 'fingerprints' are 256 bit, true random numbers. master_fingerprint is
> global to the kernel an
From: Ingo Molnar <[EMAIL PROTECTED]>
On Tue, 16 Jan 2001, Felix von Leitner wrote:
> I don't know how Linux does it, but returning the first free file
> descriptor can be implemented as O(1) operation.
to put it more accurately: the requirement is to be able to open(), use
Felix von Leitner wrote:
> I cheated. I was only talking about open().
> close() is of course more expensive then.
>
> Other than that: where does the requirement come from?
> Can't we just use a free list where we prepend closed fds and always use
> the first one on open()? That would even inc
On Tue, 16 Jan 2001, Pavel Machek wrote:
> > TWO observations:
> > - Given Linux's non-pre-emptability of the kernel i get the feeling that
> > sendfile could starve other user space programs. Imagine trying to send a
> > 1Gig file on 10Mbps pipe in one shot.
>
> Hehe, try sigkilling process do
On Tue, 16 Jan 2001, rtviado wrote:
> I got this in my logs:
>
> ip_conntrack: maximum limit of 16368 entries exceeded
>
> what does this mean, I know i can change the limits in
> /proc/sys/net/ipv4/ip_conntrack_max, but I want to know what this is for.
This means that iptable is tracking more
I'm unable to boot a 2.4.0 kernel on a system that's been running 2.2.18. It
fails early in boot with the following messages:
request-module[block-major-8]: Root fs not mounted
VFS: Cannot open root device "801" or 08:01
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mo
Hi!
The devices.txt file included in recent 2.4.x kernels
and the one at
http://www.lanana.org/docs/device-list/devices.txt
lacks infos about /dev/dspX and /dev/audioX , where
X is 2 or more.
I had to dig into the audio driver sources to figure
out that the minor number is
X * 16 + 3 for /dev/d
Ingo Molnar wrote:
> - probably the most radical solution is what i suggested, to completely
> avoid the unique-mapping of file structures to an integer range, and use
> the address of the file structure (and some cookies) as an identification.
IMO... gross. We do pretty much this exact thing in
Thus spake Ingo Molnar ([EMAIL PROTECTED]):
> > I don't know how Linux does it, but returning the first free file
> > descriptor can be implemented as O(1) operation.
> to put it more accurately: the requirement is to be able to open(), use
> and close() an unlimited number of file descriptors wit
On Tue, 16 Jan 2001, Felix von Leitner wrote:
> I don't know how Linux does it, but returning the first free file
> descriptor can be implemented as O(1) operation.
to put it more accurately: the requirement is to be able to open(), use
and close() an unlimited number of file descriptors with O
In linux-kernel, you wrote:
> Intel C440GX+ with on-board Adaptec AIC-7896 fails to boot 2.4.0:
>
> SCSI bus is being reset for host 0 channel 0
> SCSI host 0 channel 0 reset (pid 0) timed out - trying harder
> ... ad infinitum ...
>
> In contrast, this is what I get from the 2.2.17 boot:
I've go
On Tue, 16 Jan 2001, Felix von Leitner wrote:
> I don't know how Linux does it, but returning the first free file
> descriptor can be implemented as O(1) operation.
only if special allocation patters are assumed. Otherwise it cannot be a
generic O(1) solution. The first-free rule adds an implic
On 16 Jan 01 at 9:40, Urban Widmark wrote:
> On Tue, 16 Jan 2001, Rainer Mager wrote:
>
> > Hi all,
> >
> > I have a 100% reproducable bug in all of the 2.4.0 kernels including the
> > latest stable one. The issue is that if I compile the kernel to support 4GB
> > RAM (I have 1 GB) and then try
On Tue, 16 Jan 2001, Peter Samuelson wrote:
> [Ingo Molnar]
> > - probably the most radical solution is what i suggested, to
> > completely avoid the unique-mapping of file structures to an integer
> > range, and use the address of the file structure (and some cookies)
> > as an identification.
On Tue, Jan 16, 2001 at 01:04:22PM +0100, Ingo Molnar wrote:
> - a less radical solution would be to still map file structures to an
> integer range (file descriptors) and usage-maintain files per processes,
> but relax the 'allocate first non-allocated integer in the range' rule.
> I'm not sure e
Hi Linus,
Here is a patch against 2.4.1-pre7 which
1) Adds prototype for shmem_lock to mm.h
2) Again brings the fixes for the accounting. I still think it
should be applied.
Greetings
Christoph
diff -uNr 1-pre7/include/linux/mm.h m1-pre7/include/linux/mm.h
--- 1-pre7/include
[Ingo Molnar]
> - probably the most radical solution is what i suggested, to
> completely avoid the unique-mapping of file structures to an integer
> range, and use the address of the file structure (and some cookies)
> as an identification.
Careful, these must cast to non-negative integers, with
On Tue, 16 Jan 2001, Ingo Molnar wrote:
> struct lazy_filedesc {
> int fd;
> struct file *file;
> }
in fact "struct file" can (ab)used for this, no need for new structures or
new fields. Eg. file->f_flags contains the cached descriptor-information.
file->
On Tue, 16 Jan 2001, Andi Kleen wrote:
> > the 'allocate first free file descriptor number' rule for normal Unix
> > files?
> Not sure I follow. You mean dup2() ?
I'm sure you know this: when there are thousands of files open already,
much of the overhead of opening a new file comes from the ma
[Achim Herrmann]
> main.o was created using language "C": gcc -c main.c -o main.o
> and
> hwaccess.o was created using assembler: nasm -f elf hwaccess.asm -o
> hwaccess.o
>
> Is there a possibility to combine these two object files, so that I
> have a module which is loadable by insmod?
I'm no
[Felix von Leitner]
> I don't know how Linux does it, but returning the first free file
> descriptor can be implemented as O(1) operation.
How exactly? Maybe I'm being dense today. Having used up the lowest
available fd, how do you find the next-lowest one, the next open()? I
can't think of an
I had to reinstall grub on my machine (because windoze has the
bad habit of deleting any bootloader in the MBR). This is what
happened:
[...]
grub> root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
grub> setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/gru
Hi,
I'm new to device driver development under linux and I've a basic question
concerning modules, insmod and multiple object files.
Assume I have two object files "main.o" and "hwaccess.o".
main.o contains the functions init_module(), cleanup_module() and some other
functions.
hwaccess.o conta
Intel C440GX+ with on-board Adaptec AIC-7896 fails to boot 2.4.0:
SCSI bus is being reset for host 0 channel 0
SCSI host 0 channel 0 reset (pid 0) timed out - trying harder
... ad infinitum ...
In contrast, this is what I get from the 2.2.17 boot:
(scsi0) found at PCI 0/12/0
(scsi0) Wide Chann
On Tue, Jan 16, 2001 at 12:26:12PM +0100, Ingo Molnar wrote:
>
> On Tue, 16 Jan 2001, Andi Kleen wrote:
>
> > On Tue, Jan 16, 2001 at 10:48:34AM +0100, Ingo Molnar wrote:
> > > this is a safe, very fast [ O(1) ] object-permission model. (it's a
> > > variation of a former idea of yours.) A proce
On Tue, 16 Jan 2001, Andi Kleen wrote:
> On Tue, Jan 16, 2001 at 10:48:34AM +0100, Ingo Molnar wrote:
> > this is a safe, very fast [ O(1) ] object-permission model. (it's a
> > variation of a former idea of yours.) A process can pass object
> > fingerprints and kernel pointers to other processe
On Tue, Jan 16, 2001 at 10:48:34AM +0100, Ingo Molnar wrote:
> this is a safe, very fast [ O(1) ] object-permission model. (it's a
> variation of a former idea of yours.) A process can pass object
> fingerprints and kernel pointers to other processes too - thus the other
> process can access the o
Thus spake Albert D. Cahalan ([EMAIL PROTECTED]):
> Rather than combining open() with sendfile(), it could be combined
> with stat(). Since the syscall would be new anyway, it could skip
> the normal requirement about returning the next free file descriptor
> in favor of returning whatever can be
Hi!
> TWO observations:
> - Given Linux's non-pre-emptability of the kernel i get the feeling that
> sendfile could starve other user space programs. Imagine trying to send a
> 1Gig file on 10Mbps pipe in one shot.
Hehe, try sigkilling process doing that transfer. Last time I tried it
it did not
Anton Blanchard <[EMAIL PROTECTED]> writes:
>
>
> > At least for sparc it's already supported. Right now I don't feel like
> > looking into the 2.4 solution but checkout srmmu_vac_update_mmu_cache in
> > the 2.2 kernel.
>
> I killed that hack now that we align all shared mmaps to the same v
On Mon, 15 Jan 2001, Linus Torvalds wrote:
> > _syscall4 (int, sendpath, int, out_fd, char *, path, off_t *, off, size_t, size)
> You want to do a non-blocking send, so that you don't block on the
> socket, and do some simple multiplexing in your server.
>
> And "sendpath()" cannot do that with
hi,
i read the man page more carefully, it says
that the partition table is really just a
textual partition table. the __u32 came
from bsd partition table code i copied.
i also fixed the doc. the 9fat always has
the same starting sector n
On Tue, 16 Jan 2001, Tigran Aivazian wrote:
> Fixing this requires either a new filesystem type (drifs) or
> (simpler!) redesigning dri to separate common things into a separate
> dri_core thing shared amongst them.
just for completeness -- there is the 3rd option -- one could just fix the
hack w
101 - 200 of 207 matches
Mail list logo
