2011/4/19 Ariane van der Steldt :
> Your diff is reducable to:
> static struct vm_map_entry kentries[REALLY_BIG_NUMBER];
> And then managing that memory using vmmap.
Yes, more or less... But your example eats VA memory and physical
pages immediately and forever, while my diff tried to eat it on d
On Mon, Apr 18, 2011 at 7:47 AM, Christian Ehrhardt
wrote:
...
> Note that the size of the stack frame between Xintr_ioapic1 and pf_pull_hdr
> is huge (~6k). This area is filled with a 12 byte pattern that looks like
> a code address, the kernel code segment and a pushed eflags register. The
> cod
(on
+.Ox ,
+always 0)
This part makes no sense. There is no value in saying that OpenBSD
is special and will return 0. If you document it, some idiot will
depend on it.
On Mon, Apr 18, 2011 at 03:47:27PM -0600, Artur Grabowski wrote:
> A repeat of an earlier diff.
>
> Change stack and exec arguments allocation from old allocators to km_alloc(9).
> int
> fork1(struct proc *p1, int exitsig, int flags, void *stack, size_t stacksize,
> void (*func)(void *), v
On Tue, Apr 19, 2011 at 01:15:11AM +0200, Ingo Schwarze wrote:
> Hi Matthew and Joachim,
>
> Matthew Dempsky wrote on Mon, Apr 18, 2011 at 11:34:50AM -0700:
>
> > The issue here (if any) is that we over-specify the *successful*
> > return value as precisely 0, rather than generally non-negative.
On Mon, Apr 18, 2011 at 4:15 PM, Ingo Schwarze wrote:
> I like the general idea, so i'd suggest the following.
> Note that the exact wording has been chosen to be as close
> to the output of the .Rv macro as possible.
Just to voice my bike shed color preferences, I'd propose one of two
alternativ
On Mon, Apr 18, 2011 at 10:17:33AM +0200, Stefan Sperling wrote:
> On Mon, Apr 18, 2011 at 04:18:01AM +0200, Tobias Ulmer wrote:
> > On Sun, Apr 17, 2011 at 11:05:38AM +0200, Stefan Sperling wrote:
> > > On Thu, Mar 31, 2011 at 06:54:44PM +0200, Stefan Sperling wrote:
> > > > This is an attempt to
On Mon, Apr 18, 2011 at 10:24:32AM +0600, Anton Maksimenkov wrote:
> 2011/4/18 Ted Unangst :
> > +if (uvm.numof_free_kentries < 1) /*check to be safe*/
> > +panic("uvm.numof_free_kentries[%d] < 1\n",
> uvm.numof_free_kentries);
> >>> This diff would take us back to the bad old days whe
Rod Whitworth wrote Friday, April 08, 2011 1:46 AM
>
> On Fri, 8 Apr 2011 02:33:51 +0200, Florian Fuessl wrote:
>
> >upgrading GENERIC kernel from snapshot 24-Mar-2011 to -current results
> in
> >system freezes after some minutes (up to some hours) without any error
> >message, here:[...]
> 8> I
Hi Matthew and Joachim,
Matthew Dempsky wrote on Mon, Apr 18, 2011 at 11:34:50AM -0700:
> The issue here (if any) is that we over-specify the *successful*
> return value as precisely 0, rather than generally non-negative.
I like the general idea, so i'd suggest the following.
Note that the exact
On Sun, Apr 17, 2011 at 5:29 PM, Philip Guenther wrote:
> I haven't worked through all the bit-twiddling and asm, but what I
> have looks good and the abundance of regress tests that keep showing
> up in "cvs up -d" inspires confidence. With that x87-->__x87 nit, ok
> guenther@
ok matthew@ as we
A repeat of an earlier diff.
Change stack and exec arguments allocation from old allocators to km_alloc(9).
//art
Index: kern/kern_exec.c
===
RCS file: /cvs/src/sys/kern/kern_exec.c,v
retrieving revision 1.117
diff -u -r1.117 kern_
Hi all,
A number of you may have noticed the recent flurry of activity,
leading to stuff
like bigmem being turned on.. Some more good stuff is coming soon (my amd64
at my house is using 7 gigabyes of memory for buffer cache, and I'm doing builds
without touching disks..). Some really cool
On Mon, Apr 18, 2011 at 9:48 AM, Joachim Schipper
wrote:
> If
> .Fn uname
> -is successful, 0 is returned; otherwise, \-1 is returned and
> +is successful, 0 is returned; otherwise, a nonzero value (on
> +.Ox ,
> +\-1) is returned and
> .Va errno
> is set appropriately.
No, that makes our man
On Mon, Apr 18, 2011 at 6:17 AM, Kenneth R Westerback
wrote:
> r1.18 of rdist/docmd.c changed
>
>while ((len = read(fd, buf, sizeof(buf))) != (size_t)-1)
>
> to
>
>while ((len = read(fd, buf, sizeof(buf))) > 0)
>
> when fixing PR#5009. Which allowed detection of a return value of 0
The uname(3) man page suggests that checking the return value against -1
makes sense. That is not the case:
On Sun, Apr 03, 2011, Ingo Schwarze wrote to the mandoc mailing list:
> > Yuri Pankov wrote:
> >> uname(2) on Solaris (...) states:
> >>
> >> RETURN VALUES
> >> Upon successful comple
Hi,
we are seeing kernel hangs (hard reset required) under high interrupt
load (triggered by ix(4) cards). I've traced this back to an overflow
of the kernel stack. This is how the stack looks at the time of the
overflow (manual backtrace, as ddb won't show the final part):
EBP (%EBP)
If you are having trouble viewing this e-mail, Visit
www.catererswarehouse.com Caterer's Warehouse Weekly Specials
Caterer's Warehouse Special Offers
Home | Catering Supplies | Restaurant Equipment | Tabletop Specialties
Bakery Supplies | Bar Supplies | Kitchen Supplies | Commercial Furniture
| H
Da li ste veD iskoristili super fitnes ponudu?
Super prilika za fitnes opremu po najniE>oj ceni ili uz poklone!
â
Nemate vremena za treninge i veE>banje u fitnes centru? Zašto ne biste
napravili sopstvenu teretanu i veE>bali kod kuDe!
â
Odaberite najbolje fitnes rekvizite za sebe i prip
Hi,
did anyone except itojun ever use the IPsec socket options?
It currently only seems to be used by isakmpd/iked to bypass IPsec for
IKE traffic but I could not find any code that is using the other
modes like "require".
The attached diff is for testing only and is based on an old KAME ping
fr
r1.18 of rdist/docmd.c changed
while ((len = read(fd, buf, sizeof(buf))) != (size_t)-1)
to
while ((len = read(fd, buf, sizeof(buf))) > 0)
when fixing PR#5009. Which allowed detection of a return value of 0,
i.e. end of file. However len is size_t and thus does not grok -1
and th
Dear friends, how are you?
We are a China export company of capacitors, our product is very low wholesale
prices, but ensure supply of the original quality. tantalum
capacitor;[http://www.shjinpei.cn/jsp/en/class.asp] Multilayer ceramic
capacitor(high MLCC, wide
capacitance);[http://www.shji
Hi,
this removes the support to check and convert (very) old incarnations
of ffs. This old code makes diffing to fsck_ffs in freebsd harder.
We use and old filesystem in one place (the vax boot image), but that
image does not need checking, and even Miod is not sure it's actually
needed for the
On Mon, Apr 18, 2011 at 04:18:01AM +0200, Tobias Ulmer wrote:
> On Sun, Apr 17, 2011 at 11:05:38AM +0200, Stefan Sperling wrote:
> > On Thu, Mar 31, 2011 at 06:54:44PM +0200, Stefan Sperling wrote:
> > > This is an attempt to add wol support to xl(4).
> > >
> > > Unfortunately, while I have an xl(4
24 matches
Mail list logo
