:>
:> > On a related note I'm not sure if it makes sense to have the same
:> > behaviour for the first line when an interval is set as when it is
:> > invoked with no interval.
:
:...also vmstat seems to exist in a few other OSes (linux e.g). maybe they've
:fixed it already (or the netbsd/openbsd/
w I would definitely go with the chained-hash /
small-linear-array / chain / small-linear-array / chain mechanic. It
seems to be the clear winner.
-Matt
ck for our route tables in DFly, and also for listen
socket PCBs to remove choke points, and a few other things like
statistics gathering.
-Matt
Matthew Dillon
__
:Pardon my ignorance, but wouldn't so much KVM make small embedded
:devices like Soekris boards with 128 MB of physical RAM totally unusable
:then? On my net4801, running RELENG_8:
:
:vm.kmem_size: 40878080
:
:hw.physmem: 125272064
:hw.usermen: 84840448
:hw.realmem: 134217728
KVM != physical m
he pipeline hot.
-Matt
Matthew Dillon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to &
through two iterations, and compare.
If you figure out what is causing the problem I'd love an
email. I suspect it is a mapping overlap somewhere due to
the page 0 map. I just can't think of anything else it might
be.
-Matt
intermediate path element really
represents a directory and return ENOENT if it doesn't.
This situation can occur due to searches via the module search path.
-Matt
Matthew D
:What this shows is that vfork() is 3 times faster than fork() on static
:binaries, and 9 times faster on dynamic binaries. If people are
:worried about a 40% slowdown, then perhaps they'd like to investigate
:a speedup that works no matter whether its static or dynamic? There is
:a reason that p
c/bin/sh/sh count 106
object /usr/lib/libedit.so.3 count 63
object /usr/lib/libncurses.so.5 count 270
object /usr/lib/libc.so.4 count 638
Non-PLT COPY Prebindings:
object /usr/obj/usr/src/bin/sh/sh count 13
-Mat
:At 00:23 26/11/2003 -0500, Michael Edenfield wrote:
:>Static /bin/sh:
:> real385m29.977s
:> user111m58.508s
:> sys 93m14.450s
:>
:>Dynamic /bin/sh:
:> real455m44.852s
:> user113m17.807s
:> sys 103m16.509s
:
: Given that user+sys << real in both cases, it look
n to be able to do something like
that. What I am advocating is that FreeBSD-5 not marginalize and
restrict (make less flexible) basic infrastructure in order to get other
infrastructure working.
-Matt
:> is the path you've chosen to go then you have an obligation not to
:> tear out major existing system capabilities, such as the ability to
:> generate static binaries, in the process.
:
:If this is what you think has happened, you're living in some parallel
:fantasy universe.
I
h static binaries. If you want to do it wrong then ignore static
binaries. It is that simple.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
remember? :-)
:
:Cheers,
:--
:Jacques Vidrine NTT/Verio SME FreeBSD UNIX Heimdal
Just not thinking out of the box, maybe.
-Matt
Matthew Dillon
<[EMAIL P
FreeBSD,
then I certainly still have a right to post to this group.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
[EMAIL PROTE
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
er you have a dynamic root or a static root,
FreeBSD is digging itself into a hole if it cannot use these spiffy
new mechanisms with static binaries.
-Matt
Matthe
able to use
NSS for because it will break static binaries.
It is a serious logistical and planning mistake, IMHO.
-Matt
Matthew Dillon
icky. I intend to use it for all resource and
authentication lookups... password, group, services, pam equivalent,
kerberos, resolver, and so on and so forth. Hell, I think I might use
it for C locale too just to be able to rip locale out of libc.
:GAD> Many freebsd users (me for one) are still living on a modem,
:GAD> where even one bump of 1.5 meg is a significant issue...
:GAD>
:GAD> Remember that the issue we're talking about is security
:GAD> updates, not full system upgrades. "Everyone" would want
:GAD> the security updates, even if t
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubsc
:Many freebsd users (me for one) are still living on a modem,
:where even one bump of 1.5 meg is a significant issue...
:
:Remember that the issue we're talking about is security
:updates, not full system upgrades. "Everyone" would want
:the security updates, even if they're on a slow link.
:
:--
:/boot has grown quite large too and threatens to be unbounded in size as
:times go on. Shaving off the 30-40MB of size in /bin and /sbin can
:help alleviate this, even on system formatted in 5.x partition sized.
:...
:This argument wasn't the most compelling one by itself, but it played a
:part i
not saying there aren't other arguments,
just that this isn't one of them.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
_
st place.
I do not intend to make /bin or /sbin dynamic in DragonFly by default.
I don't mind adding support for those people who want it, but I am not
going to make it the default.
-Matt
:Well, there's some glue there now, but its pretty slim. What you
:advocate would swap system call numbers for doing structure reloading per
:call, which would significantly incrase the cost of the call.
:Considering that *BSD system call overhead is pretty bad as is, I don't
:think I'd be puttin
syscalls.
The userland program doesn't know the difference, it uses fstat() and
statfs() just like it always has.
-Matt
Matthew Dillon
l compatibility.
This is what I plan to do with DragonFly for *stat(), *statfs*(),
various sysctls that return structures, and so forth. Wherever it makes
sense to do it.
-Matt
:I just tried Jung-uk Kim's driver on -stable and sofar it works OK:
:
... and I just ported it to DragonFly and it works fine there too
with an ASUS K8V Motherboard. Kudos!
-Matt
___
[EMAIL PROT
:
:
:On Fri, 17 Oct 2003, Jason Dictos wrote:
:
:> 1. Had FreeBSD 5.1 system running.
:> 2. Did a cvsup get of stable (that's right, stable, so 4.9)
:> 3. Compiled make buildworld, then did a make build world, and re-compiled
:> with generic kernel
:> 4. Booted into a system which could not mount
% of the time. Don't worry, the kernel will
pre-fault pages that are already cached in memory (to a point), and
the kernel will also cluster pagein operations if actual I/O becomes
necessary.
-Matt
Ma
f_syncwrites
f_asyncwrites
f_syncreads
f_asyncreads
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
[EMAIL PROTECT
e trivially
relative to being trivially relative.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
usefull for other things too, possibly for
:security lock-downs on shell users env's without chrooting them as an
:example.
:
:-Jon
Yes, Exactly.
-Matt
Matthew Dillon
on top of the
existing ports infrastructure. It will be several months (possibly
6-12 months) before the kernelland is sufficienctly progressed to be
able to imlpement the userland VFS concept so we have a lot of time to
think about how to do it.
:> before :complaints start up. We can advertise later, if it's necessary.
:>
:> I've got a bunch of mailing lists already set up on dragonflybsd.org.
:I didn't notice. Sorry for stepping all over you.
:
:LER
:
:Larry Rosenman http://www.lerctr.org/~ler
No biggy! I w
:> I also have the disk space.
:>
:> Let me know if you are interested.
:
:I'm happy with it, but right now, until we get a bit more organized, we
:only need one yea vote: Matt's. I *don't* want to inconvenience his plans
:any (especially not when I'm really sure I don't understand them all
:yet).
must somehow become immortal or its a wasted effort is
just absurd.
Open source is the ultimate expression of Darwinism, and evolution takes
many forms, but one thing is for certain: There is no such thing as
immortality for Linux, FreeBSD, or anything else for that matter.
:> Hmm, typing this command a second time I nopw see extra info:
:> Registrant:
:> Matthew Dillon
:>41 Vicente Rd
:>Berkeley, CA 94705
:>US
:
:I've been to Matt's house before -- its real. He does have a T-1 at
:home.
:
:--
:-- David ([EMAIL PROTE
:>
:> I stupidly misspelled 'announcing' in the subject line,
:
:Well, at least you didn't misspell your name... :-)
:
:> but it's very real. Check the site out:
:>
:> http://www.dragonflybsd.org/
:
:The site looks interesting. All the kernel-level stuff is
:pretty much over my head
:
:Is it real or another troll?
:
:-Maxim
I stupidly misspelled 'announcing' in the subject line, but it's very
real. Check the site out:
http://www.dragonflybsd.org/
It's basically the reason why I've been so quiet lately. I've been
working 12 hours a day on proving t
Announcing DragonFly BSD!
http://www.dragonflybsd.org/
Hello everyone! For the last few months I have been investigating
and then working on a new approach to the BSD kernel. This has snowballed
into a far more ambitious project
Certain operational sequences fair really badly when cpu_idle_hlt
is turned off, and its definitely due to contention. I've seen this
quite a lot. I have some numbers below.
Generally speaking I think its a good idea to wake up a HLTed cpu, but
it has to be done intelligently
:How does this break the read() API? The read() API, when called
:on a NBIO fd is *supposed* to return EAGAIN, if the request cannot
:be immediately satisfied, but could be satisfied later. Right now,
:it blocks. This looks like breakage of disk I/O introducing a
:stall, when socket I/O doesn't
serland
can decide whether to block or not block on an operation
entirely independant of the OS deciding whether to block or not
block on an operation.
-Matt
Matthew Dillon
ynchronously otherwise.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
entry anything can happen after the first reported failure.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
:
:I'm really dumb when it comes to CAM, SCSI, USB, and so on, so
7; rule.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
next-server 216.240.41.12;
hardware ethernet ...;
}
host net2 {
hardware ethernet ...;
}
...
}
}
-Matt
Matthew Dillon
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
:Matthew Dillon <[EMAIL PROTECTED]> writes:
:
:> 4.x and -current use the same mechanism, except 4.x uses MFS and
:> -current uses MD.
:
:4.x uses /etc/diskless[12] while 5.x (by default) uses
:/etc/rc.d/(init)?diskless. The latter is works very differently than
:the form
I'm not sure what is occuring here but it sounds like
cockpit trouble somewhere. Make sure your NFS server is
exporting to your subnet and that it is running the
necessary services, (portmap, mountd, nfsd -t -u -n 4).
If you have another box that you can boot normally
(not
/proc procfs rw 0 0
That's basically it. You can also use /conf/base/.remove and
/conf/default/.remove files to list files to remove from the
clone. You don't have to specify a network config in your
/conf/default/etc/rc.conf because the
Well, there is something to be said for trying to avoid userland
namespace pollution, but it is still somewhat of a stretch since most
userland programs #include standard and system headers before
they #include their own, and the includes are typically done before
any code.
:02:59:24 -0800 (PST). The date/time stamp on the message that I am
:replying to is Sat, 1 Feb 2003 10:47:44 -0800 (PST). That's
:something around seven hours and forty-five minutes, unless I have
:miscalculated.
:
: Is it really normal to expect replies within that kind of a time
:fra
without an underscore), or mix with
some of the arguments named and some not (some wholely not).
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [E
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
int x;
int fubar(int x);
int
fubar(int y)
{
int x = 2;
++x;
y = 1;
return(1);
}
int
fubar2(int x)
{
++x;
return(1);
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
wit
en the choice of underlines
or leaving the arguments unnamed, I would leave them unnamed. Or I
would figure out and remove whatever broken compiler option is generating
the warning in the first place.
-Matt
:Julian Elischer writes:
:> I don't know about the protection with a '_'.
:>
:> It's not standard and usually the name matches that used in the actual
:> function.
:
:When the prototype parameter name matches a local variable, the C compiler
:(and lint) whine about clashes between names in local/g
heads involved with locating
a new task to schedule from some other cpu's run queue when the current
cpu's run-queue is empty are irrelevant because you are only eating
into cycles which would otherwise be idle anyway.
-Matt
:The cache and most of the execution hardware is shared. The execution
:units can run something like 4 instructions per clock. If the "idle"
:logical core is in a spinloop, then it is generating instructions for
:execution, so you are dividing the execution resources between one context
:that is
u that would
simply serve to wakeup the HLT. IPIs are nasty, but there are large
(power consumption) advantages to standardizing on the HLT methodology.
-Matt
Matthew Dillon
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
table.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I recently changed the swap backoff algorithm in -current and the
MFC is slated for -stable.
Try this change and see if it produces better results.
-Matt
Index: label.c
===
:Hmm, good stuff, but shouldn't something be committed anyway? I mean if it
:causes a panic just by plugging in the device that's totally unacceptable.
:I'll provide a backtrace of the crash on my computer tomorrow I suppose (I
:won't be home until then) and let people know if that's what's causing
:Backtrace would be useful since you shouldn't be getting a panic. At the
:worst, your usb reader just wouldn't work.
:
:-Nate
At worse the system will crash. The problem is that USB devices
sometimes return total garbage for the READ CAPACITY command. This
isn't CAM's fault, it is
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
:> >#define VM_METER VM_TOTAL
This change was part of a larger patch set. I have no particular
objection to adding the #define or renaming VM_TOTAL back to VM_METER,
but I *WILL* point out that even without a name change the VM cnt
structure has changed so often that for al
:...
:> is never a problem with its bounds). Other users of getbsize() in the
:> src tree but perhaps not ones in ports have been broken to match the
:> interface breakage. The usual breakage is to cast the size_t to int
:> without checking bounds.
:
:Agreed. Not a single consumer actually want
The swapctl code has been comitted. Bruce, you never supplied feedback
in regards to your original nits, but feel free to clean the code up
now that it has been comitted. All other bullets have been taken care
of.
I'm still on the fence in regards to backporting it. I would
-current another couple of days.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
:I've got this on my development box which doesn't run any services.
:I don't remember exactly what I've been doing when these appeared;
:probably printing some connection data like IPs and ports from TCB
:would help.
:
:
:Cheers,
:--=20
:Ruslan Ermilov Sysadmin and DBA,
:[EMAIL PROTECTED]
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
:>=20
:> Which appears to just be triggered by a mechanism to drop
:> bad packets. Is this correct? Is this something I should be
:> concerned about?
:>=20
:Mat
:The NetBSD code is already different:
:1.48 (augustss 15-Sep-99): /* The OHCI hardware can handle at
:most one page crossing. */
:1.48 (augustss 15-Sep-99): if (OHCI_PAGE(dataphys) ==
:dataphysend ||
:1.48 (augustss 15-Sep-99):
meone
would forward this information to the NetBSD/OpenBSD folks.
These were very serious bugs.
-Matt
:Date: Thu, 19 Dec 2002 17:11:32 -0800 (PST)
:From: Matthew Dillon <[EMAIL PROTECTED]>
:Message-Id: <[EMAIL PROTECTED]>
:To: Na
:First, the calculation of dataphysend is totally bogus.
:You can just take the physical address and add (len - 1)
:to it. You have to take the virtual address, add len - 1
:to it, and convert it to a physical address. I can
:crash my machine simply by doing a
God, my g
1a'
On the disk-on-key USB device.
Second, I believe the OpenBSD and NetBSD code is broken.
The range can be one or two pages, but the remaining bytes
may be less then one page and this has to be taken into
account.
-Matt
This is a real mess but I finally got it to work. (Note
to John: both quirk entries are absolutely necessary,
everything stalls and dies without them).
Problem #1: RA_NO_CLEAR_UA quirk required in umass.c.
Problem #2: RA_NO_CLEAR_UA quirk code is broken,
cau
-
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
-
It took a hellofalong time pulling my hair out trying to figure out why the
Fumerola disk-on-key I just bought didn't work.
First I added a Quirk entry for the standard 6-byte problem, but it didn't solve
the problem.
Finally, after slogging through an insane amount of debugging (I m
:
:In message <[EMAIL PROTECTED]>, Matthew Dillon w
:rites:
:>This commit is crashing my -current box on boot when it
:>goes to check for a core. I get the panic:
:>
:>"Negative bio_offset (-1024) on bio ..."
:>
:>Userland probably should not be
:>
:> Eh? For ATAPI and UFM devices we never send a 6 byte command to the
:> device that can fail, only 10 byte commands.
:
:I believed this was a SCSI over bulk only device.
:
:--
:B.Walter COSMO-Project http://www.cosmo-project.de
:[EMAIL PROTECTED] Usergroup
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
:
:phk 2002/12/13 14:04:45 PST
:
: Modified files:
:sys/geom geom_dev.c
: Log:
: Add a couple of KASSERTS, just in case.
:
: Revision ChangesPath
:
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
n both cases it appears that memory is being freed by one side
which is still being used by the other side but I haven't tracked down
the exact cause.
-Matt
Matthew Dillon
It took a hellofalong time pulling my hair out trying to figure out
why the Sony disk-on-key I just bought didn't work.
First I added a Quirk entry for the standard 6-byte problem, but it
didn't solve the problem.
Finally, after slogging through an insane amount of debugging (
:
:On Wed, 18 Dec 2002, Matthew Dillon wrote:
:
:> Here's another update. I cleaned things up even more, add BLOCKSIZE
:> support, and updated the manual page. It looks quite nice now.
:
:I still dislike it. It starts by adding style bugs to the Makefile
:(changing "=&
}
:> +break;
:[...]
:
:The repeated 'whichprog == foo' tests can be combined into a
:single test at the end of the loop.
They do subtly different things so I am not sure what you mean.
You need to provide some code here.
:> -
:> +
:
:?
Here's another update. I cleaned things up even more, add BLOCKSIZE
support, and updated the manual page. It looks quite nice now.
-Matt
Index: Makefile
===
RCS file: /home/nc
:Added the enum instead of is_swap* commands and changed from kvm to
:sysctl to get the swap information.
:
:Eirik Nygaard <[EMAIL PROTECTED]>
:PGP Key: 83C55EDE
All right, I found a couple more bugs and fleshed it out a bit.
You got your LINKS and MLINKS reversed and forgot a +=,
you
sysctl is much, much faster then the kvm call because
the kvm call has to run through the swap radix tree to collect the useage
information.
-Matt
Matthew Dillon
<[
wouldn't be surprised at all.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
:...
:Received: from gator.darkhorse.com (mail.darkhorse.com [209.95.33.140])
: by mx1.
:You know the person by name/alias, then? Who is it?
:
I do not know who it is, he posts through anonymous proxies.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]&g
nning the blind proxies he abuses to post, either.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Huh. Interesting. The IP_FW_ADD test threw me but now that I
look at the code more closely it is only there because IP_FW_ADD
is a valid SOPT_GET op as well as a SOPT_SET op. But FLUSH and friends
are SOPT_SET only. Now I see how it works :-)
Ha ha.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
:From [EMAIL PROTECTED] Mon Dec 16 14:00:03 2002
:...
:Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.2
:How this could be helpful in a remote upgrade scenario that has
:IPFW ABI incompatibility issues?
:
:One alternative approach would be to not compile IPFW into a
:kernel but rather have it loaded as a module. Then, you
:install new kernel, edit out ipfw_enable=3D"YES" for the time
:being, reboot
:
:How about renaming swapon(8) into swapctl(8) after this function enhancemen=
:t?
:This name reflects it's purpose much better and would be consistent with the
:other BSDs.
:
:- Christian
I think that's an excellent idea. We would have to do some
rewriting to add the expected options bu
1 - 100 of 1252 matches
Mail list logo
