Hi all,
after walking through some of NIC drivers and trying to remove check_region()
calls, i have two small questions:
1) many NIC drivers contain (in XXX_probe1 functions) check like this:
if (dev == NULL) {
dev = init_etherdev();
}
but many
Followup to: <[EMAIL PROTECTED]>
By author:Andre Hedrick <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> Nobody asked but, HDD solid state devices that could be used for booting
> would require the linking or inclusion of of non-open binaries that must
> be executed once the release
Followup to: [EMAIL PROTECTED]
By author:Andre Hedrick [EMAIL PROTECTED]
In newsgroup: linux.dev.kernel
Nobody asked but, HDD solid state devices that could be used for booting
would require the linking or inclusion of of non-open binaries that must
be executed once the release of
Title: Top 5 Internet Sites
TOP 5 Internet Web Sites
1. $1000.00 Weekly Give Away, Gaming
Newsletters,
Bad Bets section, Chat, Handy Caper's, Sportsbooks, Online Casinos
more.http://www.top100gamingsites.com
2. Computer
Systems, Desktops, Notebooks,
Mac,
Still photo, Webcams,
Not meant to offend, but it's obvious you are not grasping hardware
optimization issues relative to kernel development and performance. I
would recommend getting your hands on a bus analyzer, and testing out
some of your theories, and explore for yourself relative to these issues
with some hard
On 15 Oct 2000, H. Peter Anvin wrote:
Nobody asked but, HDD solid state devices that could be used for booting
would require the linking or inclusion of of non-open binaries that must
be executed once the release of INT13/INT19 are completed from the bios
bootstrapping. We are looking
Andrey Panin wrote:
Hi all,
after walking through some of NIC drivers and trying to remove check_region()
calls, i have two small questions:
1) many NIC drivers contain (in XXX_probe1 functions) check like this:
if (dev == NULL) {
dev = init_etherdev();
Um? Huh? This seems like mumbo-jumbo to me. With the exception of those
parts of the kernel that actually manipulate the hardware as hardware, --
which is a surprisingly small part of the kernel, even of the parts of the
kernel that look like what they do is manipulate the hardware as hardware
Hello, all:
I compile my linux module program dony.c with "-D--Kernel__ -DMODULE"
options enabled, and then insert it into kernel using "insmod dony.o" . It
stops when it tries to access a global varible "struct dony_struct
MyPrivateStruct" and complains such messages as "cannot handle page
P.S. I apologize if this driver is allready marked EXPERIMENTAL for 2.2.x
-- but I don't have the disk space right now to check, and I wanted to make
sure that, as the maintainer, my official opinion on the matter was voiced.
Its already marked experimental, no problem.
-
To unsubscribe from
how do we begin the process of getting our drivers included into the =
kernel?
See Documentation/SubmittingDrivers in a current kernel. (I've mailed you a
copy of the file offlist)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
Many thanks go to both Keith Owens, and the multitude of others
that responded to my 2.4.x boot problem. Keith sent me his
VIDEO_CHAR patch which helped track things down, and will also
prove helpful in the future as well.
The problem ended up being user error. ;o) My kernels are
compiled for
Hi,
suppose i allocate an buffer by calling kmalloc.
i want to map this buffer to user address space.
will remap_page_range will automatically map this
buffer to calling process's address space.
thanks.
__
Do You Yahoo!?
Yahoo! Messenger - Talk
On Mon, Oct 16, 2000 at 08:16:53AM +0100, Alan Cox wrote:
I've noticed this behavior for a few kernel revisions now, up to and
including 2.2.17. It would be nice to get this bug worked out before
2.2.18.
I dont think that is likely to happen. Every time someone touches the tulip
In 2.2.18pre16 an alternative USB_UHCI driver under the option
CONFIG_USB_UHCI_ALT was added. Only this one works for me, and
CONFIG_USB_UHCI throws up 50 messages a second like this one:
Oct 16 00:12:22 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 188
and leaves my mouse in an
Take your fights with me offline. You have my email address.
Jeff
Marty Fouts wrote:
Um? Huh? This seems like mumbo-jumbo to me. With the exception of those
parts of the kernel that actually manipulate the hardware as hardware, --
which is a surprisingly small part of the kernel, even
Do you know that there is actually a name for the logical fallacy behind
this sort of argument?
But please, enlighten me, what precisely about having once wrote some file
system code for Linux qualifies one as an expert on the topic of the
relative difficulty of optimizing C and C++ as used in
On Mon, 16 Oct 2000, Alan Cox wrote:
I've noticed this behavior for a few kernel revisions now, up to and
including 2.2.17. It would be nice to get this bug worked out before
2.2.18.
I dont think that is likely to happen. Every time someone touches the tulip
driver close to release they
Firs of all, as someone said, is there any other list where we can discuss this
?
It is ver off-topic here...
I messed in the discussion because I'm tired of seein people say that they don't
use
C++ because their big overheads, being slow, messed, out of programmer's control
for
low level tasks
[EMAIL PROTECTED] said:
The 'C' language can order structure members anyway it wants. It also
can add any 'fill' or alignment bytes it wants. The compiler is not
broken in this respect.
Anyone who's been following this list for a while will know not to take any
notice of Dick, especially
Actually, I spent four months at Novell profiling Chorus, MACH and TMOK
(Trusted Modular Object Kernel -- a very nice piece of work) with EMON
and an AArium profiling bus footprints -- the result. C++ kernels are
slightly slower, and hit the wall on I/O performance due to excessive
memory
I've found a few inconsistencies with the wording of some license
statements refering to "GNU public license" and similar, and have
reworded them properly to "GNU General Public License".
Please apply this to 2.4.0, it's against test9. I'll do one for
2.2.x too, and look for other such
"Stephen C. Tweedie" wrote:
Hi Jan,
On Wed, Sep 27, 2000 at 02:56:20PM +0200, Jan Kara wrote:
So I've been thinking about fixes in quota (and also writing some parts).
While we're at it, I've attached a patch which I was sent which simply
teaches quota about ext3 as a valid fs
On Sun, Oct 15, 2000 at 11:35:23PM +0100, Kenn Humborg wrote:
On Sun, Oct 15, 2000 at 09:45:11PM +0100, Alan Cox wrote:
Well, we ain't got these luxuries/complications in VAXland... Hell,
we don't even have two-level page tables :-(
Really. Ugh. I always assumed Vax had at least two
We've kind of got 1.5-level page tables. There are actually 3
page tables.
The system page table maps memory starting at 0x8000. The
P0 process
page table maps from 0x0 up and the P1 process page table maps from
0x7fff down.
And they have to be physically contiguous I guess
On Mon, 16 Oct 2000, Alan Cox wrote:
2.2.18pre16
o Finally get the m68k tree merged(Andrew McPherson
and a cast of many)
Ah. Very good.
o NFSv3 server patches merge (Dave Higgen)
This is
[EMAIL PROTECTED] said:
I've found a few inconsistencies with the wording of some license
statements refering to "GNU public license" and similar, and have
reworded them properly to "GNU General Public License".
If we're referring to it by name, we probably ought to call it the
'GNU General
Ingo Rohloff wrote:
snip
I can convert the stuff _in place_ (it actually works, anyone please
complain loudly if it shouldn't) even when my 'cryptfile' is /dev/hdax
and I don't have sizeof(/dev/hdax) space left on my hard drives.
This could be dangerous. I'm not sure that the kernel
And NOW!
To: [EMAIL PROTECTED]
cc:
Subject: Oops 2.2.x
I'm definitely conviced that in the actual kernel source 2.2.16 2.2.17
2.2.18pre15 there is a bug that generate this Oops:
Oct 12 16:32:57 giulia kernel: Unable to handle kernel paging request at virtual
address 0900841f
Oct
On Mon, 16 Oct 2000 08:50:24 -0400,
Mark Salisbury [EMAIL PROTECTED] wrote:
the original-original post was somebody asking why not make the kernel headers
C++ friendly.
all he wanted was the c++ reserved words removed from / kept out of the headers.
that way, if they for some reason want to
Hi guys,
I always test new ideas or learn about things by writing a little module
that does what I want to explore. But today I discovered that on a Red Hat
6.9 system (running test10-pre3 with everything correctly upgraded) I can
no longer compile a trivial skeleton hello.c unless I use the
We are formulating cunning plans of aggregating 2, 4 or 8 pages together
into "bigpages", telling the arch-independent code that we've got
larger pages than we really have and manipulating multiple PTEs in the
set_pte() primitive and friends.
If you ever want to get the networking behaving
See Documentation/SubmittingDrivers in a current kernel. (I've mailed you a
Speaking of that file,
Portability:Pointers are not always 32bits, people do not all have
floating point and you shouldn't use inline x86 assembler in
your driver without careful
Aren't there other examples where firmware is supplied in a struct
which is initialized to the needed binary values? Seems like Linux
doesn't need every bit of source (probably for some completely other
processor or ASIC, maybe written in FORTH) included as part of the
kernel.
Quite a few.
Hello all,
I am trying to work out a problem that I will run into if I go to a
newer kernel then 2.2.14. I am using a lucent modem in a toshiba
satellite laptop. Lucent released a bianary driver for 2.2.12 that works
with 2.2.14. To make it work with 2.2.15 or higher, you have to use a
script i
satellite laptop. Lucent released a bianary driver for 2.2.12 that works
with 2.2.14. To make it work with 2.2.15 or higher, you have to use a
script i found to mask a 2.2.14 ppp module as one for the higher kernel.
It wont work reliably in 2.2.15 even then as it misses some wake up calls
On Tue, 17 Oct 2000, Keith Owens wrote:
On Mon, 16 Oct 2000 15:29:53 +0100 (BST),
Tigran Aivazian [EMAIL PROTECTED] wrote:
static void __exit test_exit(void)
{
return;
}
module_init(test_init);
module_exit(test_exit);
# kgcc -Wall -O2 -g -c -o hello.o hello.c
hello.c:13:
ftp.uk.linux.org:/pub/people/dwmw2/pcsp/patch-pcsp-soundcore-2.4.0-test10-pre3
Thanks to Erik Inge Bolsø for porting it to 2.3.45, this saving me most of
the work.
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
On Mon, 16 Oct 2000, John Alvord wrote:
On Mon, 16 Oct 2000 14:45:03 +0200 (CEST), Igmar Palsenberg
[EMAIL PROTECTED] wrote:
I presume your driver doesn't mind if this image is unavailable.
If not, you'll need to provide a open source image to use in place
of your proprietary one.
You could do what I do with my ThinkPad 600X and Lucent modem, which is to keep
a 2.2.14 kernel available just for using the modem. Both lilo and loadlin offer
the capability of having a selection of kernels available. In fact, I usually
have at least three or four versions from which to
I've been playing with some gcc patches to detect code with undefined
behaviour of the i = i++ variety. The patch below fixes all places in
the kernel that I could find. Note that in some cases, it wasn't
entirely clear what the code intended, so I had to guess.
I haven't tested this patch at
I need help with fork() on SPARC Linux. I am trying to port my diet
libc to SPARC Linux but can't get fork() to work. Even when I copy the
fork() code from glibc verbatim, the tasks have a corrupted stack frame.
I tried to strip the init code and it looks like I broke fork in the
process.
In article [EMAIL PROTECTED] you wrote:
# kgcc -v -E -dM -Wall -O2 -g -c -o hello.o hello.c
The biggest problem with this is that you use the glibc headers (in
/usr/include) instead of the kernel headers (in /usr/src/linux/include)
kgcc -O2 -I/usr/src/linux/include -D__KERNEL__ -o hello.o
On Mon, 16 Oct 2000, Alan Cox wrote:
is in cdrecord itself, since I have seen that if the FIFO ever hits 0%
during CD burning, cdrecord has a tendency to bomb. =20
If you empty the fifo and the drive fifo you burn a coaster. Thats a feature
of CD burning and one reason I use 640Mb magneto
On Mon, 16 Oct 2000, Arjan van de Ven wrote:
In article [EMAIL PROTECTED] you wrote:
# kgcc -v -E -dM -Wall -O2 -g -c -o hello.o hello.c
The biggest problem with this is that you use the glibc headers (in
/usr/include) instead of the kernel headers (in /usr/src/linux/include)
kgcc
** Reply to message from "Jeff V. Merkey" [EMAIL PROTECTED] on Sun, 15
Oct 2000 18:06:05 -0600
The [new] and constructor/destructor operations create hidden memory
allocations in C++ that can blow performance in kernel "fast paths".
I don't consider the memory allocation that [new] and
** Reply to message from Keith Owens [EMAIL PROTECTED] on Tue, 17 Oct 2000
00:43:58 +1100
Interesting concept, linking a module with libg++. Would that be a
dynamic or static link?
If it is dynamic then you can absolutely forget about loading the
module into the kernel, there is no way
On Mon, 16 Oct 2000, Andrea Arcangeli wrote:
On Sun, Oct 15, 2000 at 03:48:55PM -0400, Jeff Garzik wrote:
Changes:
* both: we know we are in an interrupt, so
s/spin_lock_irqsave/spin_lock/
There request_irq is not called passing the SA_INTERRUPT flag so the irq
handler is recalled
Bernd Schmidt wrote:
diff -x log.build -x .* -dru linux-2.4/drivers/net/tulip/tulip_core.c
linux-2.4-fixed/drivers/net/tulip/tulip_core.c
--- linux-2.4/drivers/net/tulip/tulip_core.cMon Oct 16 13:51:23 2000
+++ linux-2.4-fixed/drivers/net/tulip/tulip_core.c Mon Oct 16 15:40:12 2000
On Mon, 16 Oct 2000, Alan Cox wrote:
Umm, doesn't cdrecord know how to address IDE devices directly?
IDE cd burners talk ATAPI. ATAPI is just a scsi variant. SCSI won the battle
at the protocol level
...
Yeah yeah yeah. What I meant was "you don't have to use ide-scsi." However,
after
On Mon, 16 Oct 2000, Jeff Garzik wrote:
--- linux-2.4/drivers/scsi/aha152x.cMon Oct 16 13:51:24 2000
+++ linux-2.4-fixed/drivers/scsi/aha152x.c Mon Oct 16 14:51:29 2000
@@ -1280,7 +1280,8 @@
scsi_unregister(shpnt);
[EMAIL PROTECTED] wrote:
If I have two identical network cards on my machine and I unregister the
driver of one
of them (say eth0) using the call "pci_unregister_driver(pdev-driver)"
where pdev is
the 'pci_dev' structure for eth0, does the device 'eth1' i.e. the other one
gets effected by
On Mon, Oct 16, 2000, David Rees [EMAIL PROTECTED] wrote:
In 2.2.18pre16 an alternative USB_UHCI driver under the option
CONFIG_USB_UHCI_ALT was added. Only this one works for me, and
CONFIG_USB_UHCI throws up 50 messages a second like this one:
Oct 16 00:12:22 spoke kernel: usb-uhci.c:
"Mike A. Harris" wrote:
On Mon, 16 Oct 2000, Alan Cox wrote:
I've noticed this behavior for a few kernel revisions now, up to and
including 2.2.17. It would be nice to get this bug worked out before
2.2.18.
I dont think that is likely to happen. Every time someone touches the tulip
ksymoops 2.3.4 on i686 2.2.17. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.2.17/ (default)
-m /boot/System.map-2.2.17 (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log
On Mon, 16 Oct 2000, Alan Cox wrote:
Its a message from the drive politely requesting cd-record to talk valid
commands. But as ide-scsi touches some commands (remapping old ones that are
not supported on ATAPI) its possible to be kernel
Umm, doesn't cdrecord know how to address IDE
Andre Hedrick wrote:
I don't understand why you say this... CompactFlash, for example, is a
solid-state HDD device, and it speaks ATA just as well as any disk.
No special binaries required.
This is my point.
www.platypustechnology.com SSD/HDD's require a firmware load to make them
Pavel,
While you should report drivers or other kernel functions
that don't work, I don't think that just saying that
something is broken is sufficient.
~Randy
Hi!
7. Obvious Projects For People (well if you have the hardware..)
* Make syncppp use new ppp code
* Fix SPX
Bernd Schmidt wrote:
+
+#define ___swab64(x) \
+({ \
+ __u64 __x = (x); \
+ ((__u64)( \
+ (__u64)(((__u64)(__x) (__u64)0x00ffULL) 56) | \
+ (__u64)(((__u64)(__x) (__u64)0xff00ULL) 40) | \
+
Does anyone have a pointer to some documents/books for the nfs-utils code ?
(i.e., code for mountd, statd etc)
Thanks.
Samar
-
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/
On Mon, 16 Oct 2000, Ricky Beam wrote:
snip
There are specific notes about the HP 7100 drives not working corectly due
to bad command translations. That was supposed to have been fixed years
ago.
Hi Ricky,
And I know it was working on this very machine some time in the past
with a 2.2.x.
This patch has many bogus corrections where new variables were created, but
the order of evaluation is already unambiguous.
For example each comma separated clause in an expression is guaranteed to be
completely evaluated before the next comma separated clause Including
Assignments.
It seems as
Hi,
I noticed that behaviour of BLKSSZGET changed between 2.2 and 2.4. One of
the users will be fdisk, as soon as it is compiled with 2.4 kernel
headers, but then fdisk will be no longer usable under 2.2!
My question now is, wouldn't it be better to use a new ioctl (like
BLKHSSZGET) and keep the
Im running my linux box as a RAS using pppd 2.3.7 on kernel version 2.2.5.
What we see is that if we disconnect more than 60 sessions in an instant
only 60 or so pppd go away and not the rest.. Secondly what we have seen is
that after there have been about more than 2 connections /
BTW, this fork program did appear to kill about 2 sun servers here...
The linux kernel v2.2.16 that they were running survived fine.
On Thu, 12 Oct 2000, Richard B. Johnson wrote:
On Thu, 12 Oct 2000, Oliver Xymoron wrote:
On Wed, 11 Oct 2000, Kiril Vidimce wrote:
My primary concern
Every closed source piece of software is unacceptable in a standard kernel
:
-hh We can't debug it
- We depend on the guys / girls that maintain the binary image
- It's a security risk.
Aren't there other examples where firmware is supplied in a struct
which is initialized to the
Ingo Rohloff wrote:
There is a paper about why it is a bad idea to use
sequence numbers for CBC IV's. I just have to find the reference to it.
Does this mean sequence as in 0,1,2,3,4 ... or does this mean
any pre-calculate-able sequence ? In the former case we might just use
a simple one way
Hi,
On Fri, Oct 13, 2000 at 12:30:49PM +0100, Malcolm Beattie wrote:
free_kiovec(1, iobuf);/* does an implicit unlock_kiovec */
It doesn't do an unmap_kiobuf(iobuf) so I don't understand where
the per-page map-count that map_user_kiobuf incremented gets
decremented again. Anyone?
Ingo Rohloff wrote:
-snip---
As an example, it is not true that CBC encryption
can use an arbitrary nonce initialization vector: it is essential
that the IV be unpredictable by the adversary. (To see this, suppose
the
On Mon, 16 Oct 2000, Andre Hedrick wrote:
Yes but there is a way to do this directly now, the question is can the
user-space apps change to go both ways.
Hi Andre,
Is there any tool / test code that you know of to 'do this directly' -
I'm wanting to try to avoid ade-scsi translation, and
David Lang wrote:
Does the kernel support multiple sound cards in one machine?
It depends on the driver and hardware, but in general yes. PCI cards
are your best bet, you can pretty much stick as many of those in your
machine as you would like, without having to worry about IRQ/DMA/ioport
David Lang wrote:
-BEGIN PGP SIGNED MESSAGE-
where can I look to find what hardware to look for/avoid?
The es1371's are especially rock solid stable. If you have PCI and its
supported, you are ok I think...
Jeff
--
Jeff Garzik| The difference
On a RedHat 7.0 stock kernel, agpgart finds the AGP aperture the first
time it's loaded, but if it's unloaded and reloaded, it gets confused
and seems to think the aperture is located at 0. At this point,
starting the Xserver (3.x or 4.x) or loading DRM drivers manually
freezes the system. SysRq
On Sat, 14 Oct 2000, David Riley wrote:
safemode wrote:
I'm just wondering if I'm the only person who has had problems with
2.4.0-test9 recording on ide-scsi cdr's?
Nobody has posted anything about it and the test10-prex changefiles don't
mention it. cdrecord reports very weird
At 01:21 PM 10/16/00, Jeff Garzik wrote:
Bernd Schmidt wrote:
diff -x log.build -x .* -dru linux-2.4/drivers/net/tulip/tulip_core.c
linux-2.4-fixed/drivers/net/tulip/tulip_core.c
--- linux-2.4/drivers/net/tulip/tulip_core.cMon Oct 16 13:51:23 2000
+++
Mark Cooke wrote:
On Mon, 16 Oct 2000, Andre Hedrick wrote:
Yes but there is a way to do this directly now, the question is can the
user-space apps change to go both ways.
Hi Andre,
Is there any tool / test code that you know of to 'do this directly' -
I'm wanting to try to avoid
Also sprach Abramo Bagnara:
}
} Isn't this more efficient?
} n = (x32) | (x32);
} n = ((n 0xLL)16) | (n 0xLL)16;
} n = ((n 0x00ff00ff00ff00ffLL)8) | (n 0xff00ff00ff00ff00LL)8;
}
} 6 shift
} 4 and
} 3 or
}
Plus 3 assigns...but they may get optimized
Hi!
While you should report drivers or other kernel functions
that don't work, I don't think that just saying that
something is broken is sufficient.
Well, that driver really is broken.
It uses tq_scheduler in strange way, so it has unbound ping times. (Up
to 20 seconds). It breaks under
On Mon, 16 Oct 2000, Douglas Gilbert wrote:
I if cdrecord bypassed the sg driver and spoke to the
cdrom driver directly. I know the CDROM_SEND_PACKET
ioctl() is in place for lk 2.4 but from which version
has it been functional in the lk 2.2 series?
But the write command is not included in
Jonathan George [EMAIL PROTECTED] writes:
This patch has many bogus corrections where new variables were created, but
the order of evaluation is already unambiguous.
For example each comma separated clause in an expression is guaranteed to be
completely evaluated before the next comma
I recently compiled 2.4.0-test10-pre3, and was torture-testing
it...I hadnt played any MIDI files in a while, so while one
was playing (on my waveblaster GM daughterboard, thru UART401),
the gave an Oops.
After doing some detective work, I found that the culprit was a
small daemon I had running
On Mon, Oct 16, 2000 at 06:23:32PM +, David Wagner wrote:
(snip)
Using SHA1(sector #) should be ok, as long as you don't expect your
plaintexts to have similar patterns. (If you do think your plaintexts
might begin with the SHA1-hashes of sector numbers, you could use a
"keyed hash",
Hi,
Concerning fdisk, luckily you are mistaken - its source says
#if defined(BLKSSZGET) defined(HAVE_blkpg_h)
so that it will not use the broken BLKSSZGET of 2.2.
??? BLKSSZGET has exactly the same ioctl number in 2.2 and 2.4, so if I
compile fdisk under 2.4 and try to use it under 2.2,
On 16 Oct 2000, Ben Pfaff wrote:
Jonathan George [EMAIL PROTECTED] writes:
This patch has many bogus corrections where new variables were created, but
the order of evaluation is already unambiguous.
For example each comma separated clause in an expression is guaranteed to be
-Original Message-
From: Ben Pfaff [mailto:[EMAIL PROTECTED]]
Jonathan George [EMAIL PROTECTED] writes:
This patch has many bogus corrections where new variables were created,
but
the order of evaluation is already unambiguous.
For example each comma separated clause in an
I will test this soon, hopefully. I move tomorrow, and will be bringing my
X environment and my audio environment into my dual P200 machine. This is
against which kernel? 2.4.0-test10 prepatch, or?
On Mon, 16 Oct 2000, James Simmons wrote:
ANyone with a MDA card on a SMP or even UP machione
-Original Message-
From: Alexander Viro [mailto:[EMAIL PROTECTED]]
[snip]
No arguments here, but proposed fixes were remarkably ugly. Example:
tmp = *p++;
*q = f(tmp, *p++);
return p;
is equivalent to more idiomatic
*q = f(p[0], p[1]);
return p+2;
And example with copying the string
Jonathan George [EMAIL PROTECTED] writes:
$ The order of evaluation of the function designator, the
$ arguments, and subexpressions within the arguments is
$ unspecified, ...
--
I sit surprised and corrected. With every version of every C compiler on
every OS I have ever
On Mon, Oct 16, 2000 at 04:47:09PM -0400, Alexander Viro wrote:
tmp = *p++;
*q = f(tmp, *p++);
return p;
is equivalent to more idiomatic
*q = f(p[0], p[1]);
return p+2;
Which gets better assembler out of various versions of gcc?
mrc
--
Mike Castle Life is like a clock:
On Mon, 16 Oct 2000, Mike Castle wrote:
On Mon, Oct 16, 2000 at 04:47:09PM -0400, Alexander Viro wrote:
tmp = *p++;
*q = f(tmp, *p++);
return p;
is equivalent to more idiomatic
*q = f(p[0], p[1]);
return p+2;
Which gets better assembler out of various versions of gcc?
Hi,
On Mon, Oct 16, 2000 at 12:08:54AM +0200, Andrea Arcangeli wrote:
The basic problem is that map_user_kiobuf tries to map those pages calling an
handle_mm_fault on their virtual addresses and it's thinking that when
handle_mm_fault returns 1 the page is mapped. That's wrong.
Good point
I haven't seen any traffic since Oct13 - is the list down ?
regards,
Per Jessen
-
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/
Andrea Arcangeli wrote:
On Sun, Oct 15, 2000 at 03:48:55PM -0400, Jeff Garzik wrote:
Changes:
* both: we know we are in an interrupt, so
s/spin_lock_irqsave/spin_lock/
There request_irq is not called passing the SA_INTERRUPT flag so the irq
handler is recalled with irqs enabled and
On Mon, Oct 16, 2000 at 04:55:08PM -0400, Ben Pfaff wrote:
$ The order of evaluation of the function designator, the
$ arguments, and subexpressions within the arguments is
$ unspecified, ...
I sit surprised and corrected. With every version of every C compiler on
every OS
On Mon, Oct 16, 2000 at 10:38:41PM +0200, Roman Zippel wrote:
[now that you make me look at this, there is a flaw in fdisk there;
fixed in 2.10p]
BLKSSZGET isn't defined for fdisk.c? :)
Indeed :-)
The current code looks like this:
- BLKSSZGET added in common.h
- in fdisk.c added
Matti Aarnio [EMAIL PROTECTED] writes:
On Mon, Oct 16, 2000 at 04:55:08PM -0400, Ben Pfaff wrote:
Yes. In practice the usual question is whether the compiler will
evaluate the operands from left to right or from right to left,
but the compiler is within its rights to evaluate the
On Mon, Oct 16, 2000 at 11:29:27AM -0700, Linus Torvalds wrote:
The page count is (or should be) sufficient, and if it weren't sufficient
that would be a bug in the swap-out handling of anonymous or shm memory. I
If the page isn't locked swap_out will unmap it from the pte and anybody will
be
On Mon, Oct 16, 2000 at 10:22:06PM +0100, Per Jessen wrote:
I haven't seen any traffic since Oct13 - is the list down ?
Back then your email address started to bounce somehow.
I have already forgotten the details, but when we get
bounces (often quite a lot), we remove
Hi Linus and Rik,
The same analysis I did for __alloc_pages() applies to
__alloc_pages_limit(), namely it can be optimized by looking at the logic
of 'page == NULL'. In both cases, of course, I checked the assembly
listing to make sure that my patch didn't make a worse code. It was always
a few
On Mon, 16 Oct 2000, Andrea Arcangeli wrote:
If the page isn't locked swap_out will unmap it from the pte and anybody will
be able to start any kind of regular VM I/O on the page.
Doesn't matter.
If you have increased the page count, the page _will_ stay in the page
cache. So everybody
201 - 300 of 335 matches
Mail list logo
