.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail
:
:* Matthew Dillon ([EMAIL PROTECTED]) wrote:
:
: felt that 8 partitions is restrictive. My main home server has 10
: and the main DragonFly box has 11.
:
: There is another solution for FreeBSD folks, however. You *DO* have
: four slices to play with. You can put
:
: Dmitry == Dmitry Marakasov [EMAIL PROTECTED] writes:
:
:Dmitry * Matthew Dillon ([EMAIL PROTECTED]) wrote:
: felt that 8 partitions is restrictive. My main home server has 10
: and the main DragonFly box has 11.
:
: There is another solution for FreeBSD folks, however. You *DO*
: have four
scratching my head a bit. This may be just as broken
as before, just in a different (and safer) way.
-Matt
Matthew Dillon
[EMAIL PROTECTED
It is interesting to note that DragonFly has had variant symlnks for
a long time, but we haven't actually found a use for them yet. No
smoking killer app has presented itself. We use varsyms in our RC
implementation kind of like uber-environment variables (rclist, rcstart,
:...
:BSD behaviour:
:- OpenBSD handles hardlinks since 3.3:
: -P Overwrite regular files before deleting them. Files
:are overwritten three times, first with the byte pattern
:0xff, then 0x00, and then 0xff again, before they are
:deleted. Files
.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail
The TSCs for each individual cpu core can drift relative to each other,
even on multi-core chips like AMD X2s. This only effects code which
uses the TSC, which isn't a whole lot. They need to be synchronized
with each other (by calculating the drift and correcting for it) when
The real culprit here is passing held mutexes to unrelated procedures
in the first place because those procedures might have to block, in
order so those procedures can release and reacquire the mutex.
That's just bad coding in my view. The unrelated procedure has no
clue as to
I'm having to tackle this issue right now in DFly. With GPT having to
start at sector 1 (no choice there), the compatible MBR in sector 0
presumably must have a slice (#1) which covers the entire disk.
But do we have to make slice #1 bootable? Could we also create a
slice #2
.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
:No.
:The first partition is the EFI GPT (0xee):
:
:% fdisk -1
:*** Working on device /dev/ad0 ***
:...
:parameters to be used for BIOS calculations are:
:cylinders=116280 heads=16 sectors/track=63 (1008 blks/cyl)
:
:Media sector size is 512
:Warning: BIOS sector numbering starts with
to point the MBR at sector 40.
The more I think about it, the more sense it makes.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
___
freebsd
for allocations up to and including PAGE_SIZE*2 bytes.
Fun, eh?
-Matt
Matthew Dillon
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org
Matthew Dillon
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
We added it basically because doing all the junk described in
previous postings in this thread in userland is a ridiculously huge
eyesore that doesn't scale and doesn't make sense when 5 minutes of
programming nets you a shiny new system call which does it all for you.
If you
booting
the live CD so those bits don't have to be re-read. Doing a direct
copy has always felt 'faster' to me then unpacking split up tar files.
-Matt
Matthew Dillon
Here's the basic problem: The kernel is currently designed for
single-threaded operation plus interrupt handling. A piece of code
in the kernel can temporarily disable certain interrupts with the
spl*() codes to cover situations where a race on some system resource
might
test case for us because it will be
fairly easy to port and fairly easy to measure performance under load.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send
: [ML] It is possible to handle these cases in VM code, by
: trapping on any access to the partial page, and allowing only those
: accesses which are withing the originally requested range. Performance
: would suck without end, though.
:
:Well it would only suck for access to that page
.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
:Matt,
:If you agree with this patch to your patch
:I'll commit the NFS fixes to 3.x
:(I'll also add this change to the 4.0 version.)
:
:*** hold/nfs_serv.cTue Jun 22 13:37
:[...]
:
:I guessed I freaked some people out when I declared that I wanted to
:work on the VM system, discussions in the first few months went with
:half of core talking to me like I didn't know jack when I do know at
:least jack, but had to come up to speed on
under the program's control. Thus most programs using
mmap() simply map the file's full size and do not try to do anything
fancy.
: Kelly
: ~[EMAIL PROTECTED]~
-Matt
Matthew Dillon
that
would cut NFS stat traffic in half.
I find it rather humorous that I always spend hours testing things that
other committers would commit without any testing whatsoever.
-Matt
Matthew Dillon
.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
for
one of those descriptors that should return EBADF!
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-ha
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
: 2. Most shell services do a good job of keeping ident reliable. They need
: to do that because most IRC networks heavily penalize clients that don't
: return any ident.
:
:This is changing. In the face of ${BIGNUM} Windoze boxes giving ident
:answers like "HAX0r", there is little point, except
:How in the world could my inetd ident service be exploited? I just fixed
:the only problematic feature, fake id, to make it not read anything but a
:regular file and not let you try to use someone else's name. I can't see
:any way that any part of it could be exploited...
Typically the
This topic has been rehashed a thousand times.
What it comes down to is that if you want to disallow overcommit, you
have to multiply the amount of swap space in the system relative to
current levels in order to get the same performance limits as you had
before. If you
:How hard would it be to add a sysctl variable that controlled whether or not
:the system would overcommit memory?
:
:-Archie
:
:___
:Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
Archie,
:
:On Tue, 13 Jul 1999 11:59:25 -0700 (PDT)
: Matthew Dillon [EMAIL PROTECTED] wrote:
:
: We could have the ability to mark processes as being more or less
: preferable as kill candidates. I'm not sure I really care anymore,
: though... there is so much disk space available now
:
: On Tue, 13 Jul 1999 11:13:49 -0700 (PDT),
: Matthew Dillon [EMAIL PROTECTED] said:
:
: Doh! Even solaris doesn't overcommit - you think it actually
: reserves data blocks for its file-backed swap? Bzzt! It uses
: an overcommit model too.
:
:Unlike 4.4BSD derived VM
the
lockup -- you could even try turning off all logging (but leaving syslog
running, i.e. turning it into a sink-null) to see if that has an effect.
-Matt
Matthew Dillon
the kernel.
:...
:-Archie
-Matt
Matthew Dillon
[EMAIL PROTECTED]
:___
:Archie Cobbs * Whistle Communica
:
:On Tue, 13 Jul 1999 14:27:54 -0700 (PDT)
: Matthew Dillon [EMAIL PROTECTED] wrote:
:
: You are assuming that the situation actually occurs. In real life,
: it will not occur unless the critical server is running away with
: memory.
:
: I have never, ever run one
the UNIX libc builtins. The UNIX libc bulitins properly assume
a more general machine configuration and it would not be appropriate to
use them for embedded work if memory use is an issue.
-Matt
Matthew Dillon
:Jason Thorpe wrote:
:
: On Tue, 13 Jul 1999 14:14:52 -0700 (PDT)
: Matthew Dillon [EMAIL PROTECTED] wrote:
:
: If you don't have the disk necessary for a standard overcommit model to
: work, you definitely do not have the disk necessary for a non-overcommit
: model to work
:On Tue, 13 Jul 1999 15:12:14 -0700 (PDT)
: Matthew Dillon [EMAIL PROTECTED] wrote:
:
: The text size of a program is irrelevant, because swap is never
: allocated for it. The data and BSS are only relevant when they
: are modified.
:
:Bzzt. BSS is relevant when accessed
ctical.
Heh heh.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
:On Tue, 13 Jul 1999 16:24:53 -0700 (PDT)
: Matthew Dillon [EMAIL PROTECTED] wrote:
:
: I'm sure the feeling is mutual. More to the point, I really seriously
: doubt that any of the core developers would consider this idea either
: because it's been rejected in the past and, so
:
:On Tue, 13 Jul 1999 16:56:26 -0700 (PDT)
: Matthew Dillon [EMAIL PROTECTED] wrote:
:
: You have to consider the probability of an event occuring, not just
: the possibility that the event might occur. If the probability is
: one in a million years, then it is not something
e runaways are common enough to cause a problem.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hacke
: On Tue, 13 Jul 1999 17:25:21 -0700 (PDT),
: Matthew Dillon [EMAIL PROTECTED] said:
:
: With today's modern high capacity disk drives, a properly configured
: multi-user system will have enough swap that running it out is difficult
: to say the least.
:
:That's wrong.
:Please
?
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
x datasize limit
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
but they would do a lot better with a watchdog
script. It makes no sense to try to build it into the kernel.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
resort mechanisms to keep your machines running.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
. If the system starts to
page (which this person's system is obviously doing), then it is doubly
a bad idea to allow a named to grow that large.
-Matt
Matthew Dillon
:On Tue, 13 Jul 1999 23:18:58 -0400 (EDT)
: John Baldwin [EMAIL PROTECTED] wrote:
:
: What does that have to do with overcommit? I student administrate a undergrad
: CS lab at a university, and when student's programs misbehaved, they generate a
: fault and are killed. The only machines
principles. It would work as well in an overcommit system as it would
in a non-overcommit system.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail
:
: Quite true. In the embedded world we preallocate memory and shape
: the programs to what is available in the system. But if we run out
: of memory we usually panic and reboot - because the code is designed
: to NOT run out of memory and thus running out of memory is a
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
r whatever it is that has your shorts all tied
:up in a knot.
:
:---
:Garance Alistair Drosehn = [EMAIL PROTECTED]
:Senior Systems Programmer or [EMAIL PROTECTED]
-Matt
Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
t close to using all available
swap, the other subsystems would be up the creek anyway so, really,
it doesn't make much sense hacking the source to allow the subsystem
to run into the wall anyway.
-Matt
in order to get better interactive
performance. e.g. working over a remote connection while
at the same time downloading a big tar file via ftp or a
browser.
-Matt
Matthew Dillon
loop and collect
statistics that way.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
tially
swappable space.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
occurs ).
Do a pstat -s before, after the initial touch, and after
the fork. If you do not see the reserved swap space jump
by 32MB after the fork, it isn't what you thought it was.
-Matt
Matthew Dillon
at you can then
mount and use normally.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hacke
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
doesn't change ). 439MB of swap verses 12MB of swap.
In that scenario, the 512MB of swap I assigned to this machine would be
dangerously low.
-Matt
Matthew Dillon
that are still
running no longer being stable. As a sysop, I would reboot a system
in such a state instantly.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send
to disable overcommit.
:
:--lyndon
If your machines aren't going to run out of swap, then the overcommit
isn't going to hurt you in a million years.
-Matt
Matthew Dillon
and not set errno properly if errno
was already set, but a perusal of the kernel code seems to indicate
that this can't happen. Very weird.
-Matt
Matthew Dillon
[EMAIL
files or swap partitions?
Or is it that weird /tmp filesystem stuff? If it normally uses swap
files and allows holes then that explains everything.
-Matt
Matthew Dillon
are
certified for any of that stuff that I know of.
What's next: A space shot? These what-if scenarios are getting
ridiculous.
-Matt
Matthew Dillon
[EMAIL PROTECTED
Matthew Dillon
[EMAIL PROTECTED]
:take great care to gracefully handle these exceptions. All the C
:programs that we've ever written also take great care in handling
:NULL returns from malloc.
:
:I have no problem
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
:Cheers,
:Vince - [EMAIL PROTECTED] - [EMAIL PROTECTED] __
To Unsubscribe: send mail to [EMAIL PROTECTED
: I know, I'm just wondering how did they get more frequency out of
:wire of the same size. I can understand it if the wire was a larger
:guage.
For twisted pair, Less power == less crosstalk. Plus the higher
bandwidth transceivers use better receivers and better pre-attenuation
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
' and reboot.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
difficult except for the mmap()
piece.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" i
assume that the data
buffer returned by malloc() is already clear. Since calloc() is not
usually used to allocate large chunks of memory, this isn't a problem.
-Matt
Matthew Dillon
is different, but almost the same size.
:
:Why is FreeBSD's file so much slower?
:
:Leif
:
:
:
:
:To Unsubscribe: send mail to [EMAIL PROTECTED]
:with "unsubscribe freebsd-hackers" in the body of the message
:
Matt
submaps?
:
:Thanks for any help.
:
:-Zhihui
The kmem_map and mb_map's can be modified from interrupts.
The other maps cannot.
-Matt
Matthew Dillon
[EMAIL PROTECTED
:
:David,
:
: Unless I am misunderstanding you, mfs does what you are
:describing.
:
: --John
No, MFS runs in supervisor mode. That mfs process that you see hanging
there is just placemarking the VM space.
-Matt
To
cpu-bound,
there is no cost to the kernel to zero memory because it pre-zero's
pages in its idle loop.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail
:
:Matthew Dillon [EMAIL PROTECTED] wrote:
:
:
: No, MFS runs in supervisor mode. That mfs process that you see hanging
: there is just placemarking the VM space.
:
: -Matt
:
:
: Well, I think there is a little more to it than that. I
store
is being implemented by MFS as a dummy block device. MFS simply copies
the data to and from the VM space of the mfs process.
-Matt
Matthew Dillon
[EMAIL PROTECTED
:Perhaps I'm missing something obvious, but since switches forward packets
:selectively per port, I would think it would be hard to sniff packets on
:any port, w/o administrative access to the switch to tell it to mirror
:data to a different port.
:
:ie, if I'm plugged into port 1, I can't see
Nice rundown of the problem!
I presume someone is going to commit this...
-Matt
Matthew Dillon
[EMAIL PROTECTED]
:*** file/apprentice.c Wed Jan 28 07:36:21 1998
more about it.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
dandy - except it's so bright it's burning holes
in my eyes at night :-(
Anyone who has one of these things know how its done?
Thanks!
-Matt
Matthew Dillon
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
.
Ah, the XFree ftp finished. Hmm. the DPMS stuff looks promising but I
don't see an I128 port yet. Shoot.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail
-then-full-sized TCP packet occassionally in a stream
but that's about it.
I think committing this would be beneficial. Would someone w/ commit
privs care to review and then commit this bit?
-Matt
Matthew
:Hi,
:
: I like this approach. I have a number of often spawned daemon
:processes that could benefit from this. One of the last process
:we debugged where we had unwanted open filedescriptors was in
:programs invoked by the cvs loginfo script.
:
: For naming convention considerations, I might
:
:It's been committed before, and broke many things (X and CVSup come to
:mind). I have it compiled in locally on a few machines but it's
:definitely not suitable for general distribution until a solution is
:found that doesn't break applications.
:
:Jason Young
:accessUS Chief Network Engineer
::It's been committed before, and broke many things (X and CVSup come to
::mind). I have it compiled in locally on a few machines but it's
::definitely not suitable for general distribution until a solution is
::found that doesn't break applications.
::
::Jason Young
::accessUS Chief Network
I believe this will solve the previously reported problems.
With the original patch if I set net.inet.tcp.sendspace=63 and tried
to run xterm from that machine to my local workstation, I got an X error.
If I set sendspace=31 the xterm process just locked up and did nothing
is likely
to be real.
There is a good chance the leakage is in nfs_serv.c, which I fixed for
-current.
I do not think those changes have been backported to -STABLE.
-Matt
Matt
same first name?
-Matt
Matthew Dillon
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
1 - 100 of 1295 matches
Mail list logo
