David O'Brien wrote:
Actually, I find it weird and counter intuitive that syslogd will not
log to the files in the config file (/etc/syslog.conf) unless they
already exists. It really feels like we are living with a programming
bug 25 years later
If I didn't want syslogd to log
David O'Brien wrote:
If it created the file itself, there would be a potential
race issue that would remain unresolved, which is hidden by
the seperation of the create and the subsequent signal.
Come again?
1. syslogd calls open(2) with O_CREAT. At this point syslogd happily
David O'Brien wrote:
On Mon, Oct 29, 2001 at 08:35:35AM -0800, Terry Lambert wrote:
No muss, no fuss. So where is the race?
Mike had the only justification so far -- that of permissions of the
file.
Think multiple instances of syslogd.
You are going to have to help me out
Sergey Babkin wrote:
Look also for TET and ETET. SVVS (the System V Verification
Suite, used for testing SVID compliance) uses TET.
TET is owned by the Open Group and they license it for money
(at least they did a couple of years ago). It's also a pain
to use.
I saved the public TET
Matthew Jacob wrote:
dumb is relative and fungible.
It's a tradeoff between doing the connection management in firmware (as with
the QLogic) or in the Kernel (as with Tachyon products mostly). It depends on
whom you believe ultimately does a better job.
Doing it in firmware allows the
Nicpon, John wrote:
Please specifically define where data goes that is sent to /dev/null
The bit bucket.
You won't have to empty the one in your machine until the year
2038, which we assume someone will come up with a way of recyling
the used bits by then (or just compressing them into bus
Stephen Montgomery-Smith wrote:
Answer 2. All the data goes into another dimension, and comes out of
/dev/random.
That would be so funny... I cat /dev/random, and I get your
files, as you delete them. 8-).
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
Jason Mawdsley wrote:
Jason Mawdsley [EMAIL PROTECTED] asks:
I am looking for a way to reserve memory, without actually
allocating the swap space.
Alfred Perlstein answers:
Just proceed normally, freebsd does overcommit such that you really
don't need to do anything
Wilko Bulte wrote:
An explanation of
why users need to reprogram their MAC's - which is rather unusual -
would help quite a bit.
Things like DECnet used to do it. And I think some server clustering
solutions might still do it.
DECNet reprogrammed the MACs with the DEC ethernet
Leo Bicknell wrote:
On Thu, Nov 08, 2001 at 02:50:44PM -0800, Terry Lambert wrote:
FreeBSD needs some basic changes for multiple MAC s to be
useful, though.
I have more than once wished to assign a separate MAC to each
virtual IP address on an interface. I have no idea how complex
Jason Mawdsley wrote:
I am creating a virtual memory manager.
Currently I am doing a
mmap(...PROT_NONE, MAP_ANON ) to reserve the memory.
then when committing the memory I am using mprotect( ...PROT_READ |
PROT_WRITE )
mmap For reservation of memory; you should
mmap the
Matthew Dillon wrote:
The small-temporary-file trick is simple: create a small temporary
file, get a file descriptor to it, remove() the file, then ftruncate()
the descriptor to the amount of space you need, mmap() it
MAP_PRIVATE, and close the descriptor. Since it is a private
Matthew Dillon wrote:
He was writing a virtual memory manger of his own that resembled
the Windows version of one he wrote, in order to port software
to UNIX (most likely Linux and not FreeBSD, if you were to look
at the web site for his company).
Simply using a pre-written file does not
PSI, Mike Smith wrote:
I am using FreeBSD 3.2 (no comments please - I've given plenty of
comments to the powers that be without results). I am currently
rewriting it in C to determine if C++ may be the problem.
Any clues??
The GCC in FreeBSD 3.2 does not support per thread exception
PSI, Mike Smith wrote:
Does anyone know exactly what _init is? An nm of my executable lists:
080486a8 ? _init
It is the lowest numeric address (before _start and main) so I would
assume it is some sort of program initialization code. But when trying
to determine the cause of a kernel
Chris Ptacek wrote:
I am trying to malloc a large amount of memory for a KLD during load and the
malloc keeps failing. I am trying to malloc 64-128MB for a memory pool for
a project I am working on. My system has 196MB of memory and the KLD is
loaded at startup so I am relativly sure that I
Martin Kaeske wrote:
Hello
Because i want to learn more about the BSD-kernel i bought
the book The Design and Implementation of the 4.4BSD Operating
System [McKusick, et.al.]. Now i come across the topic
Buffer Management and i have a question: Is it possible
that a call to bread() can
Maxim Konovalov wrote:
Alfred, John, thanks you very much for your answers. I expected
something similar. Btw are there any smart ways to find out does
underlying FS support inode concept or not? Yes, I know about
vnode.v_tag, but comparing it with VT_UFS/VT_NFS/VT_MFS etc does not
look OK
Kenneth D. Merry wrote:
[ ... transmit checksum offload ... ]
You've got things confused. I think that may be a limitation of some
SysKonnect boards, but certainly isn't a Tigon limitation.
Yes, it's not Tigon chipset specific.
Tigon boards come with 512KB, 1MB, or 2MB (never seen one of
While investigating a problem, I noticed that the IPSEC code
is initializing the sp -- even when no one is using IPSEC.
Is there a good reason why this is not late-bound, and the
IPSEC code is initializing and copying and checking the
security policy pointer, even in the absense of actual use
of
On a related topic, there appears to be a code error in the
IPSEC code.
Specifically, the priv flag is set to 1 if the user is root
and the socket is non-null (this lets the code be called
from the bridging code as well, so ignore the first half of
the if test, and concentrate on the uid == 0
Eric Anderson wrote:
Oh, well, I thought you said 10mb/s, not 10MB/s .. that makes
it a bit different. I wonder if it could still be a tcp window
size or something.. Try these sysctl's on C:
vfs.nfs.gatherdelay=0
vfs.nfs.async=1
vfs.vmiodirenable=1
Alfred stated that he had seen some
Eugene M. Kim wrote:
What would be the best way to allocate:
1) a VM page whose physical address falls within a certain boundary, and
2) a VM object whose pages are contiguous in physical address space?
Background:
The !@*%^*!#^%*!#^$!@ Intel 810/815 graphics controller requires its
Eugene M. Kim wrote:
Thank you for the reply.
I also found contigmalloc() shortly after I posted the original question
(what an embarrassment ;-p), then met another restriction: Because these
memory regions are to be accessed by a userland process (X server), they
have to be somehow
hi,
is there any utility that can read a bsd FS from win/dos?
thank you
THere are two implementations of the Heidemann framework for
Windows, using the IFSMgr (Installable File System Manager)
interface.
The first was implemented in 1996 or so by Artisoft (I was
one of the engineers).
Alex Newman wrote:
2) It would allow you to more efficently have ssl proxy boxes infront of an
array of webservers. This is useful if you had for instance a hardware
crypto card in the ssl proxy. Currently the only decent way I know to do
this today is with linux+stunnel since it has
Yar Tikhiy wrote:
Hi everybody,
The current utmp(5) manpage language (not markup)
has a number of drawbacks and errors:
o There is no information for programmers on the actual structure
of the files the page describes.
It is opaque. You are not supposed to access it directly, you
Matt Dillon wrote:
Nobody in their right mind uses a struct sockaddr_in or any other
struct sock* type of structure without zeroing it first. I suppose
we can document that in the man pages, but we certainly should not go
hacking up the kernel code to work around bad
David Malone wrote:
I was using FreeBSD a while ago, suddenly a lot of messages show up:
Limiting closed port RST responses from 224 to 200 packets per seconds.
These messages persist even after reboot. What happened? What should I do?
Could someone be port scanning you? Another
Alfred Perlstein wrote:
Hmm, well the GENERIC default is some mathematical operation on
maxusers. We really ought to make this scale as a default relative
to the amount of ram in the system, rather than some low hardcoded
value. NetBSD has some stuff for this in their buffercache sizing
Leo Bicknell wrote:
On Fri, Nov 30, 2001 at 10:29:28AM -0800, Luigi Rizzo wrote:
It is not a big deal to move the default to 32 or 64k, and I'd
vote for that, but if a sysadmin is unable to have a look at this,
then the problem is in the sysadmin, not in FreeBSD!
I disagree, on two
David Malone wrote:
On Tue, Dec 04, 2001 at 08:08:34AM -0500, Dragon Fire wrote:
I was trolling around the FreeBSD kernel source and the dev directory and
noticed there is no bdevsw structure and no block driver files. Is
everything implemented in terms of character devices now? Looks like
Brooks Davis wrote:
What I'd been thinking was that I could write a magic string over the
beginning of the MBR since I'm never going to try and boot these disks.
That would let me detect uninitalized drives as well as out of date
partitioning schemes. Are there any problems to look out for
Alexey Zelkin wrote:
According to mail archive, work on supporting wide-char functions was in
progress some time but then stopped.
May be is there some results of this work somewhere? Continue will better
than beginning from scratch.
Check out Citrus[1] project's CVS Repo. They have
Brooks Davis wrote:
It would be easiest for you to create a partition table on the
disk, and steal a table entry with a magic partition type to
indicate that either the LBA or CHS data was actually version or
type information, etc..
The thing I'm worried about there is that some smart
Matthew Dillon wrote:
These changes are performance fixes, not security fixes. I consider
them fairly significant performance fixes, but these bugs have been in
the TCP stack for literally a whole year without an outcry so I don't
see much justification for putting them
Tim Wiess wrote:
Alexander,
I had experienced this problem before. It is most likely that you are running
out of page table pages. Try changing NKPT in /sys/i386/include/pmap.h to 64.
That worked for me.
tim
On Wed, Dec 05, 2001 at 03:57:22PM +0300, Varshavchick Alexander wrote:
Hi,
David Xu wrote:
It will be still a defacto, because Linux distributions will always
install tuned version of Linux kernel as default
Tuned for what?
while FreeBSD not, the default GENERIC FreeBSD kernel's performace
sucks,
For what application?
and ordinary user will find FreeBSD is
Varshavchick Alexander wrote:
For this to work, you really MUST address the machdep.c problems.
So how can it be done, are there any patches for machdep.c, or is it
solved in 4.4-stable kernel?
Matt Dillon took a sideways stab at addressing a bit of these
issues. They didn't do everything
Nicolas Souchu wrote:
Hi VM developers,
Has anyone already some useful utils to develop a VM pager for FreeBSD?
The KGI port project is progressing and is now up to the point that I have
to handle the VM events as done in Linux.
http://www.freebsd.org/~nsouch/ggiport.html
Your
Yung-Sheng Tang wrote:
I am setting up a multicast router. Recompiling kernel with MROUTING
option and enabling mrouted are done. Basically, my multicast AP runs
well, but if that AP and mrouted run on the same machine, forwarded
packets would get udp checksum error. Here is the result from
Dmitry Konyshev wrote:
For some odd reason I need to load another OS (no matter which one,
everything that known about it is its boot sector number)
at the end of the reboot syscall. Could someone please explain how to
switch processor to real mode and continue program execution from some
Jonathan Lemon wrote:
In article local.mail.freebsd-hackers/[EMAIL PROTECTED] you write:
Really, it boils down to the allocation systems needing rewrite,
and (painful as this is to say) a move away from type stable
memory, to permit reuse, rather than static purposing of large
blocks:
Leo Bicknell wrote:
Would result in what machines not booting? As long as a 64M PC
can boot (even if it has only 10 Meg free for user apps) that's ok
in my book. If we're still trying to boot on 4, 8, or 16 meg
machines that's just dumb.
Ugh, save me from the Novell decision that lost UNIX
Nicolas Souchu wrote:
From my reading of the code, all it is is a pseudo device that
permits you to establish/remove memory mappings for various regions
of the graphics card memory, which may or may not be apertured,
into process address space, as a file buffer mapping.
[ ... ]
As you
Yung-Sheng Tang wrote:
I am sorry that I don't get what you mean well. The multicast-sending
AP, mrouted and tcpdump all run on the same machine. From tcpdump
result, the multicast AP gives the right checksum, whereas
encapsulating module(?) gives the wrong checksum, right? So, What next
I
Dmitry Konyshev wrote:
[ ... reboot with new active partition ... ]
I thought of this way, but it might seem strange for a user if her
computer would want to reboot without any obvious reason. I'll keep
this way in mind for the case I fail to implement it in more user-friendly
manner. :)
Ronald G Minnich wrote:
I saw an example of switching in real mode in linux' sources (it looks
pretty clear) and thouhgt it is possible to do the same under FreeBSD.
The problem is I'm absolutely lost in FreeBSD's physical memory management
implementation (page tables and directory and so
Ian Dowse wrote:
[ ... booting another OS that is either real mode or requires the
use of a real mode bootstrap, at FreeBSD shutdown ... ]
Yeah, I attempted something like this a few years ago without much
success. I've just updated the code to compile on -stable, and it
seems to
rick norman wrote:
What would be nice would be to load balance on a per connection
basis, not a per packet basis, between the two modems.
Any ideas how to do this ?
This whole thread is a bit odd, in that the DSL lines in question
are going to go back to the same DSLAM, and therefore end up
Poul-Henning Kamp wrote:
Most likely he means a per-open(2) opaque datum that is kept in
struct file and passed to the underlying routines.
Sorry, unbelievably bad at explaining myself. Per-open data is what i
meant. The reason I'm interested is it would make a full nvidia driver
port
Poul-Henning Kamp wrote:
The issue is non-trivial to fix because we currently don't pass
dup(2) events through the vnode layer.
Are you sure this is even necessary?
They are talking about per-open, not per-fd-instance data,
which could easily exclude dup, dup2, and fcntl(f_DUPFD).
Poul-Henning Kamp wrote:
Speaking for myself, first open and final close would be all I need for
the nvidia driver - though i'm sure tracking dup/dup2/fcntl would be
preferable in the general case.
first open/last close has been the UNIX way for decades...
I think he still means per
Alfred Perlstein wrote:
I'd be glad to assist in any way possible to get this integrated,
we've really been wanting this for various reasons (mostly linnex
compat) let me know if you're too busy and I can try to take over
from your existing work. Point being, I want this done ASAP. :)
Not
This patch will break backward compatability with existing scripts.
Since it is an easy matter to call inet_aton() on the buffer, and
then call gethostbyname() only if inet_aton() returns INADDR_NONE
(which would allow either a host name or an IP address to be used),
please use this approach
Dima Dorfman wrote:
Here's an updated patch which is a result of comments from a few
people. The changes are: (a) deconfuse the usage message by not
naming two arguments as hostname (that was sloppiness on my part),
and (b) remove a redundant inet_aton call (gethostbyname(3) will DTRT
with
Peter Pentchev wrote:
This is why the inte_aton() call is still necessary.
[snip]
Please call inet_aton(), and then _only_ if that fails, call the
gethostbyname().
How about inet_pton() and getnameinfo()?
You know, I first thought of this, but then I backed off it.
The problem is that
Evan Sarmiento wrote:
Hello,
I've been reading this thread. I made the augustments to the
patch so that it first checks if it is an IP address, if it is not,
it then tries to see if it is a hostname. If neither are true
it exits with an error.
Hope this is what you're looking for,
Mike Smith wrote:
Er, you don't seem to understand how PCI interrupts work.
You must (for now) pass RF_SHAREABLE in; eventually the PCI code will
stick it there for you anyway. All PCI interrupts are shareable; you
can't ask for an unshared vector; you get the one you're given, and you
Bernd Walter wrote:
A PCI slot has 4 irq lines named INTA to INTD.
Yes.
On PCs all slots share the same 4 physical irqs and the lines are
hardwired on the board in alternating order to each slot.
On newer motherboards, post the Intel SErver Products Division
PCI motherboards, from a year or
Hiten Pandya wrote:
i wanted to ask if there were any _plans_ to port
JFS (Journaled File System) to FreeBSD...
Not unless you have plans. When I was an IBM employee, they would
not change the license, and so it's impossible to ship a CDROM
where it's the boot FS, or boxes on which it is the
Alfred Perlstein wrote:
[ ... Hiten wants someone to GPLify FreeBSD ... ]
I'm glad you took the time to read the marketting literature.
The problem is that porting it is going to be a bit more complicated
than just dumping it into src/gnu.
Feel free to take a shot at porting it though,
Hiten Pandya wrote:
the license issues dont really affect us...
after all we have an src/gnu directory... thats what
it is for... dumping GPL'ed stuff
and talking about GPL, we can even publish the code
as the GPL license states... after all we are an
open Source Project, but if we
Greg Lehey wrote:
Since then, it has become possible for the loader to load modules
before booting the kernel. This means that, theoretically, it would
be possible to have a JFS root file system. Given the strong
opposition to the GPL in some factions of the FreeBSD project, I don't
see
Greg Lehey wrote:
FS porting to FreeBSD is actually pretty trivial(*), though some
transactioning changes to the FreeBSD VFS layer consumers (the
system calls and NFS server code) would be necessary to make
the journal roll-back function correctly, following a failure.
(*) Trivial:
Danny Braniss wrote:
well, if it's not software it must be hardware problem (true or false ?)
the test:
video capture (using a modified meteor driver)
doing full size 24bit colour, the meteor would complain about FIFO errors
(which probably mean that the dma did not finish in time -
Maxim Sobolev wrote:
OK, I load the kernel from the JFS. I mount the root FS, which
is a JFS. I read the module jfs.ko from the JFS so that I can
mount the root FS, which is a JFS, so I can read the module jfs.ko
from the JFS so that I can mount the root FS, which is a JFS, so I
can
Peter Wemm wrote:
It is not a problem. The *kernel* does not load jfs.ko, it is loader
itself. There is no reason why a trivial non-gpl jfs reader couldn't be
written for boot2 and loader if the need was great enough. Or have /boot
as a seperate file system (eg: UFS or FAT32). We do this
Danny Braniss wrote:
It looks like IRQ sharing is the only issue here.
Q: are all interrupt handlers for the shared irq called, or only the
'correct' one?
All interrupt handlers are polled -- asked if they have work to do,
on the basis of having caused the interrupt.
Some cards do not
Greg Lehey wrote:
Of course. But you're missing the point: ufs is *not* a port, it has
been with BSD since the beginning. There is a similar list of items
for JFS which would need to be addressed, with the additional issue of
the fact that it was not designed for FreeBSD.
I maintain that
Warner Losh wrote:
In message [EMAIL PROTECTED] Terry Lambert writes:
: Some cards do not have a hardware I caused an interrupt register,
: and use a differential (e.g. ring head vs. tail inequal after
: interrupt) to tell if there is work to do. If these cards were to
: share interrupts
Warner Losh wrote:
I was tired and confused when I read your message. I thought you were
describing the lance chips.
No problem... I've fallen victim to that same thing myself. As
I'm sure people will attest at great volume... 8^).
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
Mike Smith wrote:
It might be more realistic to say that PCI tries to discourage the use of
interrupts, and hardware vendors haven't really gotten the message.
8^). That's because there is no more important task for your CPU
to do than to poll devices to see if they need to do I/O; what the
Matthew Dillon wrote:
[ ... ]
I would appreciate other VM gurus taking a look at the
vm_page_set_validclean() changes.
[ ... ]
Not to appoint myself a guru or anything...
+#if 1
+ if ((base (DEV_BSIZE - 1)) || (size (DEV_BSIZE - 1))) {
+ int adj;
+
+
Matthew Dillon wrote:
Hmm. Well, my code is definitely broken. My 'adj' calculation is
all wrong. However, my size calculation appears to be correct.
(size - adj) is the size of the block after the base has been adjusted
to the next full chunk. The number of chunks we then
Dag-Erling Smorgrav wrote:
Poul-Henning Kamp [EMAIL PROTECTED] writes:
There exists a patch for adding a mode to our floppy driver to
add DEC RX50 media handling.
Clearly a job for Jessem, don't you think? :)
Kids can be cruel. 8^) 8^).
-- Terry
To Unsubscribe: send mail to [EMAIL
Peter Jeremy wrote:
Since JFS has come up again... Are there any papers that explain how
to integrate a new filesystem into FreeBSD? The relevant chapter in
the FreeBSD Developers' Handbook (16) is a bit terse :-).
Specifically, I'm looking at being able to read/write 2BSD filesystems
on
Rafter Man wrote:
1. Is there a way to hide a user from other users? Fx programs
like w, who, users, netstat, top, ps all show what other users
are doing.
The most common approach to this is to run the exterior services
in a jail (see: man jail). When the user logs into the jail,
they do not
Brooks Davis wrote:
There was a commit to current a few hours ago disabling hardware
checksums on recieve due to corruption problems. It will be MFC'd in
three days though it's a two line fix so you could apply it your self:
Greg Lehey wrote:
Do you have small images of this FS, as well as header files that
are redistributable (e.g. BSD license) and/or code?
If you have the tools sources (e.g. newfs, fsck, etc.), this would
be useful, as well, since I could vnconfig a device and recreate an
empty FS image
David Greenman wrote:
I believe you will find that the problem is related to the firmware
handling of VLAN tagging, and that the problem only exists if VLAN
tagging is enabled.
You would believe wrongly, then, because the problem that I was seeing did
not involve VLAN tags.
OK; it was
Greg Lehey wrote:
Unfortunately, it's still copyrighted. You need an SCO license; want
to go and get one of them? It doesn't cost anything, but I can't give
the software to anybody who hasn't agreed to the conditions.
8.4(b) says you can't give it to anyone, even if they do have the
David Greenman wrote:
Alfred Perlstein wrote:
You're probably incorrect, it doesn't matter if vlan tags are active
or not, it's most likely wheather or not the firmware is being asked
to handle them at all.
I would think it would get the checksum wrong most of the time if that
were the
Hiten Pandya wrote:
I found this piece of code in boot0.s, is it possible
if you could explain me a bit about it.
.set NHRDRV,0x475# Number of hard drives
The hex value comes out to: 1141.
Does that mean, that this is the amound of maximum
hard drives a user can have on
D J Hawkey Jr wrote:
Hello All.
The subject asks it all. Sorry if this is off-topic.
I won't answer the other questions because they were already
answered. The subject question, though..
The Attic is the directory where deleted files are moved.
This is necessary, since a soruce code
David Greenman wrote:
In any case, disabling it is what ClickArray ended up doing, as well,
for the Tigon II, until the firmware could be fixed.
We're talking about the Tigon III (bge driver for Broadcom BCM5700/BCM5701).
Crap. Thanks for the info.
Have you manually calculated the
John Baldwin wrote:
No. It's the offset in memory of the number of hard drives in the BIOS. The
BIOS has a data segment at 0x40, and at 0x40:0x75 (whose physical address is
0x475) it has a byte which is a count of the number of hard drives installed.
Specifically, Hiten, see:
Page
Peter Jeremy wrote:
I'm specifically looking at 2.11BSD - which is architecturally UFS but
various sizes and constants are different (eg fewer direct/indirect
blocks in the inode). In some ways this simplifies things (it may be
possible to re-use much or all of the FreeBSD UFS code) but it
Anthony Schneider wrote:
Well, the reason I brought up $USER inheritance is that on linux, $USER is root
after an su to root, whereas on FreeBSD, the $USER is the same as before the su.
Not really thinking, I thought that perhaps that refleted the inherited $UID,
which I was wrong about.
Tony wrote:
1. JFS only operates on meta-data ... It does not log file data or
recover this data to a consistent state. [JFS overview]
Yes.
The logging style introduces a synchronous write to the log disk
into each inode or vfs operation that modifies meta-data. [JFS
Zhihui Zhang wrote:
What are the backing objects of the stack and heap area of a process's
address space? When are they created? I saw the code vm_map_insert(), but
the object argument given is NULL.
Anonymous pages: swap.
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
Lamont Granquist wrote:
Can anyone give a brief overview (or point to one) of what a FS in FreeBSD
needs to do to interact with the rest of the OS? The general picture I've
got is of some code which interacts with the VFS layer above it and the
block I/O layer down below it. It is this
Dave Reyenga wrote:
How about writing a new filesystem based on UFS? This would save all of the
hassle that JFS would bring: licensing, porting time, etc. Of course, it
would likely bust any compatibility desired.
What I'm thinking is a filesystem that takes the current UFS and improves
Alfred Perlstein wrote:
By the way the journaling filesystems don't neccessary guarantee that
you won't need fsck: for example, if VXFS crashes at a particularly
bad moment, it will require you to do fsck -o full which is as slow
as the fsck on traditional UFS.
Yeah, but that's not
Leo Bicknell wrote:
If no one else has figured this mess out, I'll do it and write a
page for the handbook. If someone else has, please clue me in, and
if necessary I'll still write that handbook page. :-) It would be
very nice if it was simple to make FreeBSD sendmail SSL and
authenticate
Richard Sharpe wrote:
Well, it turns out that there are two problems with what I suggested: 1,
signals are lossy, in that if multiple signals occur, only one might be
delivered; and 2, there is no place to store any signal-related
information in the kernel, in any case.
The KQueue delivery
Mike Smith wrote:
I've done most of the gruntwork of making AIO a loadable system.
I'd appreciate some feedback and testing, especially since I know
of no programs which use AIO.
Where's the demand-load of the aio module? Are you going to trap ENOSYS
in the libc side of things?
Anjali Kulkarni wrote:
I have tried this too, it makes absoutely no difference at all. My mallocs
fail after a certain no. of runs of my code(and there is no memory leak),
and there was no difference by increasing MAXDSIZ/DFLDSIZ.
You were asking how to increase your VM space.
What you
Matthew Dillon wrote:
new-reno was artifically limiting the max number of in-transit
packets to 4. This is probably why the USB ethernet worked
with 4.3, but it destroyed TCP performance for everything else
and was removed.
I don't think there is kernel solution to the
Matthew Dillon wrote:
KVM is only 1G, and a lot of is used-up. You cannot allocate
(directly map) hundreds of megabytes of kernel memory.
You can crank up the KVA space, though the handbook is wrong for
-release, and woefully out of date for -current.
You can also do big allocations,
401 - 500 of 1638 matches
Mail list logo
