It seems Vallo Kallaste wrote:
On Tue, Apr 13, 1999 at 10:58:45PM +0200, Soren Schmidt s...@freebsd.dk
wrote:
Yep that is exactly what it means, however the driver in -current
doesn't take advantage of it yet, but its on my TODO list.
The reason why I put in this verbosity, is so I can
-Original Message-
From: Mikhail Teterin [SMTP:m...@misha.cisco.com]
Sent: Wednesday, April 14, 1999 12:45 AM
To: curr...@freebsd.org
Subject: Re: swap-related problems
Well, this is just an implementation detail, is not it? I don't
mean to critisize, or anything, but
On Wed, 14 Apr 1999, Ladavac Marino wrote:
-Original Message-
From: Mikhail Teterin [SMTP:m...@misha.cisco.com]
Sent: Wednesday, April 14, 1999 12:45 AM
To: curr...@freebsd.org
Subject:Re: swap-related problems
Well, this is just an implementation detail,
In message 199904132245.saa93...@misha.cisco.com, Mikhail Teterin writes:
Poul-Henning Kamp once wrote:
Well, this is just an implementation detail, is not it? I don't
mean to critisize, or anything, but such thing as no available
memory is a fairly intuitive... Coming down, again, the malloc
On Wed, 14 Apr 1999, Alfred Perlstein wrote:
On Wed, 14 Apr 1999, Ladavac Marino wrote:
-Original Message-
From: Mikhail Teterin [SMTP:m...@misha.cisco.com]
Sent: Wednesday, April 14, 1999 12:45 AM
To: curr...@freebsd.org
Subject: Re: swap-related problems
On Wed, 14 Apr 1999, Poul-Henning Kamp wrote:
In message 199904132245.saa93...@misha.cisco.com, Mikhail Teterin writes:
Poul-Henning Kamp once wrote:
Well, this is just an implementation detail, is not it? I don't
mean to critisize, or anything, but such thing as no available
memory is a
Poul-Henning Kamp once stated:
=Well, this is just an implementation detail, is not it? I don't
=mean to critisize, or anything, but such thing as no available
=memory is a fairly intuitive... Coming down, again, the malloc
=should return a usable memory if available and NULL if it's not.
=Is not
Motomichi Matsuzaki wrote:
The patch gzip+uuencoded is following.
Do you know of any problems resulting from applying this patch? I
think it's way past the time of getting it in the tree, and if there
are still any problems with it, we have to track them down and fix
them.
Anyone on -current
Ladavac Marino wrote:
Another strategy is to reserve the swap space as soon as it is
allocated by the program. This strategy is much more conservative and
inherently safer, but it needs much more space: for instance, if you
have a program with WSS of a gigabyte and you want to
On Wed, 14 Apr 1999, Mikhail Teterin wrote:
Poul-Henning Kamp once stated:
=Well, this is just an implementation detail, is not it? I don't
=mean to critisize, or anything, but such thing as no available
=memory is a fairly intuitive... Coming down, again, the malloc
=should return a
Chuck Robey once stated:
=He's not talking about an artificial limit, he's talking about another
=user making off with all the memory. This sounds very bizarre, how can
=you possibly ask the system to predict what other user's are going to
=ask for, in advance? You can't possibly get absolute
Mikhail Teterin wrote:
All I want is that a program gets NULL from malloc if there is no memory
available. I find that to be a very fundamental thing about malloc.
In response, me and others are told at different times:
. there is no such thing as no memory available (!!!)
In message 199904141314.jaa24...@kot.ne.mediaone.net, Mikhail Teterin writes:
Poul-Henning Kamp once stated:
=Well, this is just an implementation detail, is not it? I don't
=mean to critisize, or anything, but such thing as no available
=memory is a fairly intuitive... Coming down, again, the
On Wed, Apr 14, 1999 at 10:24:38PM +0900, Daniel C. Sobral wrote:
Motomichi Matsuzaki wrote:
The patch gzip+uuencoded is following.
Do you know of any problems resulting from applying this patch?
I'm not sure if this applys to _this_ patch, but a couple of
months ago I took some
Hello Soren and other -current users,
I've used your new ATA/ATAPI driver flawlessly through the 4th version.
I was not able to get past the 'changing root device to wd0s1a' message
with version 5, so I just went back to the wd driver. Last nigh I tried
version 6 and ran into the same problem. I
Poul-Henning Kamp once stated:
=malloc() on FreeBSD returns NULL when it cannot allocate the memory
=asked for.
=If you have an example where this is not the case I would VERY
=much like to see it.
I believe, a number of examples were given, when the use of the non-NULL
pointer returned by
In message 199904141501.laa25...@kot.ne.mediaone.net, Mikhail Teterin writes:
Poul-Henning Kamp once stated:
=malloc() on FreeBSD returns NULL when it cannot allocate the memory
=asked for.
=If you have an example where this is not the case I would VERY
=much like to see it.
I believe, a number
-Original Message-
From: Daniel C. Sobral [SMTP:d...@newsguy.com]
Sent: Wednesday, April 14, 1999 3:04 PM
To: Ladavac Marino
Cc: 'm...@aldan.algebra.com'; curr...@freebsd.org
Subject: Re: swap-related problems
Ladavac Marino wrote:
Another strategy is to
A while ago on -current, I posted a reference to a paper on lottery
scheduling in FreeBSD. It allows you to provide scheduling weightings
that (on average) share the CPU as described.
It is also used by the UC-Berkeley CSUA on their shell account machines.
-Original Message-
From: Mikhail Teterin [SMTP:m...@kot.ne.mediaone.net]
Sent: Wednesday, April 14, 1999 5:01 PM
To: curr...@freebsd.org
Subject: Re: swap-related problems
They then, rightfully exclaimed:
. but should not malloc() have returned me NULL?
And the
Harold Gutch wrote:
I'm not sure if this applys to _this_ patch, but a couple of
months ago I took some 3.0-patches and backported them to 2.2.
They had the problem of using the Joliet extensions when mounting
a hybrid-CD (a CD with Joliet and RockRidge extensions).
This latest patch is
Hi,
I'm getting the 'blocks of NULLs in NFS-mounted files' problem repeatably
with last night's -current (cvsup'd at Wed Apr 14 04:02:34 BST 1999)
running both on server and client (except that the client's kernel is 24hrs
older than that).
It happens during a kernel build on the client, so both
Ladavac Marino once wrote:
[ML] Sadly, in the memory overcommit situation, there is no way to
know whether a pointer returned by malloc will cause a process demise
or not. The pointer is valid, but the swap area mapping is defered
until the page is dirtied (basically, the pointer points to a
From: Harold Gutch lo...@foobar.franken.de
Subject: Re: kern/5038: FreeBSD can't read MS Joliet CDs.
Date: Wed, 14 Apr 1999 16:45:48 +0200
logix On Wed, Apr 14, 1999 at 10:24:38PM +0900, Daniel C. Sobral wrote:
logix Motomichi Matsuzaki wrote:
logixThe patch gzip+uuencoded is following.
On Thu, Apr 15, 1999 at 02:17:36AM +0900, Motomichi Matsuzaki wrote:
From: Harold Gutch lo...@foobar.franken.de
logix I'm not sure if this applys to _this_ patch, but a couple of
logix months ago I took some 3.0-patches and backported them to 2.2.
logix They had the problem of using the Joliet
The problem Mr. Pallfreeman was seeing are related to how I was
building the arp-reply based on the sources arp_hrd type. I never
expected to see a token-ring arp arrive over an ethernet interface.
Therefore the arp code was trying to check for and collect the
source route that the arp took on
Okay, that one is just a little too strong. It won't allow
a FreeBSD token-ring station to arp-reply to an ethernet station
on the other side of a broken translational bridge. This one
will.
Larry Lile
l...@stdio.com
On Wed, 14 Apr 1999, Larry Lile wrote:
The problem Mr. Pallfreeman was
From: Daniel C. Sobral d...@newsguy.com
Subject: Re: kern/5038: FreeBSD can't read MS Joliet CDs.
Date: Thu, 15 Apr 1999 02:40:58 +0900
dcs 2. Only Page 00 Unicode is shown (for Joliet CDs).
dcs ...
dcs Note.
dcs Byung's patch passes Unicode transparently.
dcs So CJK filenames are
:Hi,
:
:I'm getting the 'blocks of NULLs in NFS-mounted files' problem repeatably
:with last night's -current (cvsup'd at Wed Apr 14 04:02:34 BST 1999)
:running both on server and client (except that the client's kernel is 24hrs
:older than that).
:
:It happens during a kernel build on the client,
: All I want is that a program gets NULL from malloc if there is no memory
: available. I find that to be a very fundamental thing about malloc.
: Do you have a solution? We don't.
Make an sbrk variant which will pre-allocate backing store.
setenv MALLOC_PREALLOCATE
Not so hard.
To
In message 14100.61923.427423.153...@avalon.east, Anthony Kimball writes:
: All I want is that a program gets NULL from malloc if there is no memory
: available. I find that to be a very fundamental thing about malloc.
: Do you have a solution? We don't.
Make an sbrk variant which will
Quoth Poul-Henning Kamp on Wed, 14 April:
:
: 1. Demonstrate the need.
Well, it's only needed if you want to be able to reliably execute ANSI
C code according to spec. I personally don't care. I'd be surprised
if core didn't though. I would suspect that it would be deemed worthy
of someone's
On Wed, 14 Apr 1999, Anthony Kimball wrote:
Quoth Poul-Henning Kamp on Wed, 14 April:
:
: 1. Demonstrate the need.
Well, it's only needed if you want to be able to reliably execute ANSI
C code according to spec. I personally don't care. I'd be surprised
if core didn't though. I would
As Bob Bishop wrote ...
I'm getting the 'blocks of NULLs in NFS-mounted files' problem repeatably
with last night's -current (cvsup'd at Wed Apr 14 04:02:34 BST 1999)
running both on server and client (except that the client's kernel is 24hrs
older than that).
It happens during a kernel
Quoth Chuck Robey on Wed, 14 April:
: ... just so the one guy to
: complain *at all*
Someone is always the first person to recognize a defect. Until
others do, they stand alone.
: ...can not lose sleep over something that has causes no
: problems at all with any ANSI code in a properly sized
While doing a ``make -DWANT_AOUT world'' I'm seeing the following:
=== libgcc_r
c++ -O -pipe -march=pentium
-I/usr/src/gnu/lib/libgcc_r/../../../contrib/egcs/gcc/config
-I/usr/src/gnu/lib/libgcc_r/../../../contrib/egcs/gcc -I. -fexceptions
-DIN_GCC -D_PTHREADS
In message 19990414234749.a42...@hal.mpn.cp.philips.com Jos Backus writes:
: - I don't understand the wording of the most recent paragraph:
:
: Note cc -aout has been broken since the conversion to egcs. If
: you have rebuilt things like XFree86 a.out libraries, you should
:
On Wed, 14 Apr 1999 01:21:20 Bret Ford wrote:
On Tue, 13 Apr 1999 18:34:25 Ilya Naumov wrote:
Hello Gianmarco,
Thursday, April 08, 1999, 7:49:52 AM, you wrote:
GG ftp on 4.0-very-current (post egcs make world) randomly hangs during
GG sessions...
GG I never succeded in
On Wed, Apr 14, 1999 at 03:57:32PM -0600, Warner Losh wrote:
What it means is that cc -aout has been broken since the conversion to
egcs, and now it is supposedly working.
I see ``supposedly'' sounds about right :)
Don't know about building an aout world.
According to my system, no... I
On Wed, 14 Apr 1999 15:22:22 EST, Anthony Kimball wrote:
: 3. Send patches.
And I certainly don't care enough to do that!-)
So, what? You're just arguing for fun? If so, then you and everyone else
doing like wise can just piss the hell off.
Ciao,
Sheldon.
To Unsubscribe: send mail to
Quoth Sheldon Hearn on Thu, 15 April:
:
: : 3. Send patches.
:
: And I certainly don't care enough to do that!-)
:
: So, what? You're just arguing for fun? If so, then you and everyone else
: doing like wise can just piss the hell off.
[redirected to chat]
No, I'm trying to contribute
On Wed, Apr 14, 1999 at 02:55:27PM -0500, Anthony Kimball wrote:
: All I want is that a program gets NULL from malloc if there is no memory
: available. I find that to be a very fundamental thing about malloc.
: Do you have a solution? We don't.
Make an sbrk variant which will
Sheldon Hearn once wrote:
: 3. Send patches.
And I certainly don't care enough to do that!-)
So, what? You're just arguing for fun? If so, then you and everyone
else doing like wise can just piss the hell off.
I, for one, was arguing because I saw a number of people ask about
this over
Mikhail Teterin wrote:
Sheldon Hearn once wrote:
: 3. Send patches.
And I certainly don't care enough to do that!-)
So, what? You're just arguing for fun? If so, then you and everyone
else doing like wise can just piss the hell off.
I, for one, was arguing because I saw a
On Thu, 15 Apr 1999, Andrew Reilly wrote:
On Wed, Apr 14, 1999 at 02:55:27PM -0500, Anthony Kimball wrote:
: All I want is that a program gets NULL from malloc if there is no memory
: available. I find that to be a very fundamental thing about malloc.
: Do you have a solution? We
Steve Kargl once wrote:
Then, submit your patches to fix the problem preferably with a knob to
turn your patches on/off. From the discussion, I hope you're prepared
to deal with the following scenario:
I'll be prepared... I don't think it should be a compile time option,
though. May be
On Wed, 14 Apr 1999, Mikhail Teterin wrote:
Steve Kargl once wrote:
/usr/ports/devel/libxalloc
/usr/ports/devel/libmalloc
/usr/ports/devel/libdlmalloc
I do not see how they can guarantee the usability of the returned
memory with the current kernel. There apparently is no way of
- I don't understand the wording of the most recent paragraph:
Note cc -aout has been broken since the conversion to egcs. If
you have rebuilt things like XFree86 a.out libraries, you should
rebuild them again or things (including netscape) will not work.
Some have
I do not see how they can guarantee the usability of the returned
memory with the current kernel. There apparently is no way of
knowing at malloc time if the memory can be used. Worse then that,
it may be possible to use it at malloc time, but unless your program
runs and touches every page,
On Wed, 14 Apr 1999, Poul-Henning Kamp wrote:
In message 199904141501.laa25...@kot.ne.mediaone.net, Mikhail Teterin
writes:
Poul-Henning Kamp once stated:
=malloc() on FreeBSD returns NULL when it cannot allocate the memory
=asked for.
=If you have an example where this is not the case
On Wed, Apr 14, 1999 at 01:12:00PM -0400, a little birdie told me
that Mikhail Teterin remarked
Aha, now its clearer. May be, since we are do not conform anyway,
we can design some clever way of notifying a program rather then
SIGKILL-ing it?
Perhaps, SIGBUS? Something, a program can
On Wed, 14 Apr 1999, Poul-Henning Kamp wrote:
In message 14100.61923.427423.153...@avalon.east, Anthony Kimball writes:
: All I want is that a program gets NULL from malloc if there is no memory
: available. I find that to be a very fundamental thing about malloc.
: Do you have a
A signal handler is not guaranteed to work. It must be written such that it
does not require a new page of memory. Some possible problems here are the
stack growing, writing on a new page in the data segment, etc. I'm not familiar
enough with the VM system, but if you couldn't create a new swap
On Wed, 14 Apr 1999, Anthony Kimball wrote:
Quoth Poul-Henning Kamp on Wed, 14 April:
:
: 1. Demonstrate the need.
Well, it's only needed if you want to be able to reliably execute ANSI
C code according to spec. I personally don't care. I'd be surprised
if core didn't though. I would
I'm not doing this, damnit ;)
Then can we end this stupid thread already?
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Mikhail Teterin m...@misha.cisco.com wrote:
Worse then that,
it may be possible to use it at malloc time, but unless your program
runs and touches every page, the memory may not be available later.
If you run and touch every page, you are guaranteed to have the
memory available, but you also
Quoth Brian Feldman on Wed, 14 April:
:
: ACTUALLY it would still break ANSI because the malloc itself would crash
: the program, instead of touching the memory manually.
The point here is that malloc can return null when it fails to allocate.
I might mention that Andrew Reilly's suggestion is
WARNING - WARNING
WARNING - WARNING
WARNING - WARNING
Do not use this patch unless you are willing to lose whole
filesystems!
WARNING
: If it's true that cc -aout is broken (.section in an a.out .o file? Hm.), how
: can one rebuild things like XFree86 a.out libraries, when make world fails?
What it means is that cc -aout has been broken since the conversion to
egcs, and now it is supposedly working.
Known breakage includes:
*
Thomas Schuerger wrote in message ID
199904131923.vaa21...@wurzelausix.cs.uni-sb.de:
cvsup is mostly based on disk (and network) I/O, so there shouldn't
be a problem with properly updating the GUI. Someone said it is
done in a separate process, so I still wonder why the GUI is updated
so
In message 199904142340.taa96...@misha.cisco.com Mikhail Teterin writes:
: Then, one can write a safe malloc, which will install the signal
: handler, and touch every page in the the memory referenced by the
: to-be-returned pointer. If the signal handler is invoked in the
: progress, the
Warner Losh once stated:
=: Then, one can write a safe malloc, which will install the signal
=: handler, and touch every page in the the memory referenced by the
=: to-be-returned pointer. If the signal handler is invoked in the
=: progress, the to-be-returned memory must be returned back to the
Anthony Kimball wrote:
: All I want is that a program gets NULL from malloc if there is no memory
: available. I find that to be a very fundamental thing about malloc.
: Do you have a solution? We don't.
Make an sbrk variant which will pre-allocate backing store.
setenv
Mikhail Teterin m...@kot.ne.mediaone.net wrote:
That's my point! I advocate the use of some _other_ signal. Something
catchable.
As soon as you allow a catchable signal, you create a potential
deadlock situation. See my previous mail.
In case of resource shortage the malloc should be
64 matches
Mail list logo
