Like all performance items (especially VM), it depends on the hardware and
the load. On systems with small TLBs it helps more than with large TLBs. With
software that needs access to lots of different areas the TLB gets more traffic
so large ones help more. The answer for your firefox browser
?
...
Andrew Duane
Juniper Networks
+1 978-589-0551 (o)
+1 603-770-7088 (m)
adu...@juniper.net
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd
to rethink this in the 25 years
since
...
Andrew Duane
Juniper Networks
+1 978-589-0551 (o)
+1 603-770-7088 (m)
adu...@juniper.net
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
.)
...
Andrew Duane
Juniper Networks
+1 978-589-0551 (o)
+1 603-770-7088 (m)
adu...@juniper.net
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr
MNAMELEN is used to bound the Mount NAMe LENgth, and is used in many many
places. It may seem to work fine, but there are lots of utilities and such that
will almost certainly fail managing it. Search the source code for MNAMELEN.
...
Andrew Duane
Juniper
.
...
Andrew Duane
Juniper Networks
o +1 978 589 0551
m +1 603-770-7088
adu...@juniper.net
-Original Message-
From: owner-freebsd-hack...@freebsd.org [mailto:owner-freebsd-
hack...@freebsd.org] On Behalf Of Ed Schouten
Sent: Tuesday, November 08
Add a 0x0d to the end of the string (0xa = LF, 0xd = CR)
...
Andrew Duane
Juniper Networks
o +1 978 589 0551
m +1 603-770-7088
adu...@juniper.net
-Original Message-
From: owner-freebsd-hack...@freebsd.org [mailto:owner-freebsd-
hack
variables for the time being.
...
Andrew Duane
Juniper Networks
o +1 978 589 0551
m +1 603-770-7088
adu...@juniper.net
-Original Message-
From: John Baldwin [mailto:j...@freebsd.org]
Sent: Friday, September 09, 2011 8:32 AM
To: freebsd-a...@freebsd.org
Cc
.
...
Andrew Duane
Juniper Networks
o +1 978 589 0551
m +1 603-770-7088
adu...@juniper.net
-Original Message-
From: Peter Wemm [mailto:pe...@wemm.org]
Sent: Thursday, September 08, 2011 6:48 PM
To: Peter Grehan
Cc: Andrew Duane; freebsd-hackers@freebsd.org
*/
Reasonable? Unreasonable? Insane?
--
Andrew Duane Juniper Networks
978-589-0551 10 Technology Park Dr
adu...@juniper.net Westford, MA 01886-3418
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
, but nothing makes
any forward progress.
Sending SIGUSR1, SIGUSR2, or SIGABRT seem to work fine, as does any signal if
the core dump is going to a local filesystem.
Before I dig into this apparent deadlock, just wondering if it's been seen
before.
...
Andrew Duane
Damien Fleuriot wrote:
Hello list,
We've got these boxes at work running FreeBSD 8.1-STABLE amd64 and
serving as firewalls and openvpn gateways.
We use CARP interfaces to provide an active-passive fault tolerant
system.
Today, we received a nagios alert from the master box
the device to the filesystem code. Our implementation uses a
platform sysctl that checks the incoming device name against some hardware or
software settings. Ick. I don't know enough about device/GEOM calls to do it
better though.
...
Andrew Duane
Juniper Networks
o +1
...@freebsd.org]
Sent: Friday, April 08, 2011 11:23 AM
To: Andrew Duane
Cc: Bruce Evans; freebsd...@freebsd.org; FreeBSD Hackers;
freebsd-s...@freebsd.org
Subject: Re: retry mounting with ro when rw fails
on 08/04/2011 15:36 Andrew Duane said the following:
What I was hoping to do was design
filesystems instead, to save space and complexity.
--
Andrew Duane Juniper Networks
978-589-0551 10 Technology Park Dr
adu...@juniper.net Westford, MA 01886-3418
From: owner-freebsd-hack...@freebsd.org [owner-freebsd-hack
AFAIK, FreeBSD does not really detect read-only media. This was something I had
to add as a small project here at work, and was considering cleaning up to try
to get into CURRENT. If there's a real need for it, I could speed that up.
--
Andrew Duane Juniper Networks
978-589-0551
will not be able to complete. Once that is done, any
attempt to open a file for writing fails.
--
Andrew Duane Juniper Networks
978-589-0551 10 Technology Park Dr
adu...@juniper.net Westford, MA 01886-3418
From: Andriy Gapon
...
Andrew Duane
Juniper Networks
o +1 978 589 0551
m +1 603-770-7088
adu...@juniper.net
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any
, and those shouldn't change behaviour if someone uses /dev/null as a
test file. It seems pretty trivial to update it, so why not make it behave the
same.
--
Andrew Duane Juniper Networks
978-589-0551 10 Technology Park Dr
adu...@juniper.net Westford, MA 01886-3418
I've never seen any such thing, but I've done similar things a lot. I'd say
malloc/read the whole file in and use a decrementing pointer to return the
previous character.
--
Andrew Duane Juniper Networks
978-589-0551 10 Technology Park Dr
adu...@juniper.net
. It seems as if maybe the 1 is coming from
sbrk(0) which is just returning the value of curbrk (which is correct, and not
even close to 1).
Does this ring any bells?
--
Andrew Duane Juniper Networks
978-589-0551 10 Technology Park Dr
adu...@juniper.net Westford, MA 01886
the manuals say.
Am I missing something?
--
Andrew Duane Juniper Networks
978-589-0551 10 Technology Park Dr
adu...@juniper.net Westford, MA 01886-3418
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org
You *should* be able to use device1s2a:/ as a syntax, but I noticed a bug in
our old loader code that parses devicenames like that where it wouldn't work
correctly with unit numbers. I don't know if that bug is still around, but
setting currdev did work around it.
/Andrew
-Original
owner-freebsd-hack...@freebsd.org wrote:
On Thu, 6 May 2010, Boris Kochergin wrote:
My experience with bad memory is that if it causes the machine to
crash, it won't always happen while the machine is running the same
process (or kernel thread)--so look for it crashing in a wide
variety of
owner-freebsd-hack...@freebsd.org wrote:
Hello,
I'm asking if FreeBSD is safe regarding dead store elimination made
by gcc?
By example, in crypto drivers, sensitive datas are cleared by a
bzero() after use to avoid potential leakages. But the bzero() by
itself is useless, is it removed
purpose computing.
--Artem
I believe I know of one such company... :-)
--
Andrew Duane Juniper Networks
978-589-0551 10 Technology Park Dr
adu...@juniper.net Westford, MA 01886-3418
___
freebsd-hackers@freebsd.org
power-off handler to be called at the system shutdown */
EVENTHANDLER_REGISTER(shutdown_final, jsrxnle_poweroff_devices, NULL,
SHUTDOWN_PRI_LAST + 10);
The howto argument can be checked for RB_POWEROFF:
if (howto RB_POWEROFF) {
/* Spin Down */
}
--
Andrew Duane
Well, there are always Juniper Networks boxes :-)
-Original Message-
From: [EMAIL PROTECTED] on behalf of Matthias Apitz
Sent: Tue 8/5/2008 4:05 AM
To: freebsd-hackers@freebsd.org
Subject: Fwd: Q: case studies about scalable,enterprise-class firewall w/
IPFilter
Hello,
I've posted
I may have asked this once before, but are any NOR flash drivers
available in FreeBSD? I have support that I put into the bootstrap I'm
building, interfaced to libstand, but it is read-only, and far from
useful for a real UFS.
--
Andrew Duane Juniper Networks
978-589-0551
Obvious question: is your stack set up properly, and is it big enough?
It could be that you haven't set up a bigger kernel stack yet, and have
overrun the small boot stack that the processor was running on. Do you
know what the stack pointer is? If it is a few bytes below a page
boundary, then
Well, if the system stops accessing RAM, you had better make sure that *all*
the instructions you need are already loaded into the L1 and L2 caches.
Otherwise you won't be able to turn RAM back on. That would involve carefully
preloading everything through use of the system's appropriate
31 matches
Mail list logo
