Geoff Glasson wrote:
> I'm trying to port the Linux i810 Direct Rendering Interface ( DRI ) kernel
> module to FreeBSD. I have reached the point where the thing compiles, and I
> can load it as a kernel module, but it can't find the graphics device.
>
> Through a process of elimination I have com
Russell Cattelan wrote:
> On Sat, 2003-07-26 at 07:12, Daniel Lang wrote:
> > Bruce M Simpson wrote on Sat, Jul 26, 2003 at 10:06:36AM +0100:
> > > On Fri, Jul 25, 2003 at 01:06:28PM -0500, Russell Cattelan wrote:
> > > > How does one set the serial speed of the console.
> > >
> > > Does specifying
Paulo Roberto wrote:
> Sorry hackers, I have posted this to [EMAIL PROTECTED], but got no
> answer...
>
> I did set my mainboard BIOS to use ECP transfer mode (dma 3 & irq 7). I
> edited my kernel to:
>
> device ppc0 at isa? flags 0x8 irq 7
>
> (is there a way to declare the dma I want to use? c
Joe Marcus Clarke wrote:
> On Mon, 2003-07-28 at 12:18, Aeefyu wrote:
> > i.e. Broadcom 440x NIC support for FreeBSD 4.x and 5.x (as found on
> > latest Dell's Notebooks - mine is a 8500)
> >
> > Would anyone be so kind to enlighten me on the the current status?
> > Last I heard of developments be
"M. Warner Losh" wrote:
> In message: <[EMAIL PROTECTED]>
> JacobRhoden <[EMAIL PROTECTED]> writes:
> : I am trying to get a device working which uses ucom, and the ucom code has no
> : comments whatsoever, I am able to work bits out, I was wondering if there was
> : any sort of documen
Kai Mosebach wrote:
> Trying to compile sapdb fails on a -CURRENT system build yesterday.
>
> On a system from 22.July it compiled fine.
>
> Any ideas ?
This is pretty ugly, but put a space before the ::'s on that
line.
-- Terry
___
[EMAIL PROTECTED]
Ryan Sommers wrote:
> When making a system call to the kernel why is it necessary to push the
> syscall value onto the stack when you don't call another function?
The stack is visible in both user space and kernel space; in
general, the register space won't be, unless you are on an
architecture wi
Chris BeHanna wrote:
> What about
>
> test%201/mnt/test%201 ufs ro 0 0
>
> ?
> Ugly, yes, but that's how a lot of tools escape spaces.
"%" is almost infinitely more likely in a path than "\"; better
to use the "\" than the "%" mechanism. Also, the parser can
b LALR
John-Mark Gurney wrote:
> Ruben de Groot wrote this message on Fri, Aug 01, 2003 at 10:15 +0200:
> > On Fri, Aug 01, 2003 at 04:33:08AM +0200, mh typed:
> > The following comparison is probably bogus, but can anybody explain the
> > huge difference?
>
> It's called micro optimization. Linux feels
Simon Barner wrote:
> The attached patch will allow blanks and tabs for file systems and
> path names, as long as the are protected by a '\'.
>
> For the old fstab style, blanks and tabs are not allowed as delimiters
> (as it was in the old implementation).
You need to add '\\' to the delimited l
Matthew Dillon wrote:
> I think the ultimate performance solution is to have some explicitly
> shared memory between kerneland and userland and store the arguments,
> error code, and return value there. Being a fairly small package of
> memory multi-threading would not be an issue
"S.Gopinath" wrote:
> > I'm required to run a.out binaries like foxplus
> > in a recent Intel based hardware. I have chosen
> > FreeBSD 5.1 and successfuly installed. But I could
> > not run a.out binaries like Foxplus. I tried it by
> > load ibcs modules and aout modules in /boot/kernel
> > direct
maillist bsd wrote:
> Is it there have IP Network Multipathing failover on FreeBSD..?? how to do so??
Look for VRRP in /usr/ports/net.
-- Terry
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe,
Kris Kennaway wrote:
> On Thu, Aug 14, 2003 at 03:14:27PM +0530, S.Gopinath wrote:
> > > I'm required to run a.out binaries like foxplus
> > > in a recent Intel based hardware. I have chosen
> > > FreeBSD 5.1 and successfuly installed. But I could
> > > not run a.out binaries like Foxplus. I tried
"S.Gopinath" wrote:
> > $ foxplus
> > /usr/lib/foxplus/no87: 1: Syntax error: newline unexpected (expecting ")")
> > /usr/lib/foxplus/foxplus.pr: 1: Syntax error: word unexpected (expecting
> > ")")
> > $ file /usr/lib/foxplus/no87
> > /usr/lib/foxplus/no87: Microsoft a.out separate pure segmented
Attila Nagy wrote:
> Pawel Jakub Dawidek wrote:
> > It'll be, but probably in read-write mode on one machine and read-only
> > mode on rest machines, because you don't export file systems here, but
> > disk devices.
>
> This doesn't work on a shared SCSI bus, so I suspect sharing the device
> on t
Attila Nagy wrote:
> Terry Lambert wrote:
> > It works on firewire and it works on a dual port RAID array (as a
> > separate box containing the RAID array).
>
> What does 'it' means? I guess it's not UFS, but the pure ability of
> sharing a device on a b
Charles Howse wrote:
> I'm a hobbyist, and for my personal education, I would like to learn how
> to install FBSD from an existing filesystem, rather than from FTP or CD.
>
> My intention is to copy the files to a directory on the second HDD of my
> present FBSD system, and point sysinstall to tha
Max Clark wrote:
> Ohh, that's an interesting snag. I was under the impression that 5.x w/ PAE
> could address more than 4GB of Ram.
The kernel being able to address the RAM does not meant that
the KVA+UVA space is larger than 4G. At best, you could take
the uiomove/copyin/copyout performance hit
Geoff Buckingham wrote:
> On Thu, Sep 04, 2003 at 01:12:45AM -0700, Terry Lambert wrote:
> > Yes. Limit the number of CG bitmaps you examine simultaneously,
> > and make the operation multiple pass over the disk. This is not
> > that hard a modification to fsck, and
Denis Troshin wrote:
> Almost every package I install requires a few other packages. This
> 'idea of using dependent packages' turns FreeBSD (and other
> unix-systems) to an ugly monster.
You're right. The authors of the offending software packages
should not do that. It's going t
David Gilbert wrote:
> > "Poul-Henning" == Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
> Poul-Henning> I am not sure I would advocate 64k blocks yet.
> Poul-Henning> I tend to stick with 32k block, 4k fragment myself.
>
> That reminds me... has anyone thought of designing the system to have
Barry Bouwsma wrote:
> Would anyone care to explain why the following simple patch could be
> enough to wedge my machine solid? (My original hack-patches without
> any console printf() debuggery did the same thing within seconds, as
> well...) All it does is notify the console whenever a serial p
Clifton Royston wrote:
> For those who don't know what I'm talking about, try executing "host
> thisdomainhasneverexistedandneverwill.com", or any other domain you'd
> care to make up in .com or .net. Verisign has abused the trust placed
> in them to operate a root name server, by creating wildc
[EMAIL PROTECTED] wrote:
> sendto in send_tcp_raw: sendto(3, packet, 40, 0, X.X.X.X, 16) => No buffer
> space available
Your interface is down. This happens all the time.
If you use PPP on a dialup modem with a normal net connection,
and unplug the modem while you are doing a ping, you will see
Mike Durian wrote:
> I'm trying to implement a serial protocol that is timing sensitive.
> I'm noticing things like drains and reads and blocking until the
> next kernel tick. I believe this is due to the lbolt sleeps
> in the tty.c code.
>
> It looks like I can avoid these sleeps if isbackground
Deepak Jain wrote:
> Is there a utility/hack/patch that would allow a diligent sysadmin to obtain
> which specific TCP connections are generating retransmits and receiving
> packet drops? netstat will show me drops on an interface, but not on a
> specific source/dest pair?
>
> I am guessing someth
Barry Bouwsma wrote:
> You see, what I'm attempting to do, without knowing what I'm doing,
> is to implement the TIOCMIWAIT ioctl that apparently exists in Linux,
> to notify a userland program that there's been a status change on one
> or more of the modem status lines, and eliminate the need to p
Daniel Eischen wrote:
> > > If you are using libkse or
> > > libthr, you will get a partial byte count and not zero because
> > > the tape driver returns the (partial) bytes written. So exiting
> > > the loop in libc_r and returning 0 would only seem to correct
> > > the "problem" for libc_r.
>
>
Dan Nelson wrote:
> > These types of statistics aren't kept.
> >
> > They usually do not make it into commercial product distributions for
> > performance reasons, and because every byte added to a tcpcb
> > structure is one byte less that can be used for something else. In
> > practice, adding 134
Deepak Jain wrote:
> If the tcpcb struct were expanded/changed and the various increments were
> added in the appropriate packet pushing code, this would work right? Is
> there something non-obvious that one would need to worry about to undertake
> such a project?
Your overhead would be slightly h
Peter Jeremy wrote:
> On Sun, Sep 28, 2003 at 06:14:25PM -0400, Sergey Babkin wrote:
> >BTW, I have another related issue too: since at least 4.7
> >all the disk device nodes have charcater device entries in /dev.
>
> 'block' vs 'character' has nothing to do with random or sequential
> access and
earthman wrote:
> how to allocate some memory chunk
> in user space memory from kernel code?
> how to do it correctly?
If your intent is to allocate a chunk of memory which is shared
between your kernel and a single process in user space, the
normal way of doing this is to allocate the memory to a
Pawel Jakub Dawidek wrote:
> On Mon, Sep 29, 2003 at 06:56:13PM +0300, Peter Pentchev wrote:
> +> I mean, won't the application's memory manager attempt to allocate the
> +> next chunk of memory right over the region that you have stolen with
> +> this brk(2) invocation? Thus, when the application
Bruce M Simpson wrote:
> Now that I think on this a bit more, a sysctl might be a better place to
> put this, but it seemed to belong with the i386_vm86() bits, rather than
> polluting initcpu.c right away.
The important thing is to allow the kernel to intermediate and
control allocation of counte
Bruce M Simpson wrote:
> On Wed, Oct 01, 2003 at 11:39:36AM +0200, Grumble wrote:
> > >>However, I am not allowed to use the RDPMC instruction from ring 3
> > >>because the PCE (Performance-monitoring Counters Enable) bit is not set.
> > >
> > >You can do it with /dev/perfmon. man 4 perfmon.
> >
>
Julian Elischer wrote:
> On Mon, 6 Oct 2003, Leo Bicknell wrote:
> > In a message written on Sun, Oct 05, 2003 at 08:11:05PM -0600, Nick Rogness wrote:
> > > In addition to keeping your NAT translations (as suggested by
> > > Wes), you need to also keep routes for those entries as well, so
Luigi Rizzo wrote:
> On Tue, Oct 07, 2003 at 06:17:04PM -0400, [EMAIL PROTECTED] wrote:
> > We did some intensive profiling of our application. It does not seem like
> > we are depending on clock ticks for any calculations.
> >
> > On the other hand we notice that our slow iterations happen almost
"Giovanni P. Tirloni" wrote:
> I'm studying the network stack and now I'm confronted with something
> called netisr. It seems ether_demux puts the packet in a netisr queue
> instead of passing it directly to ip_input (if that was the packet's
> type). Is this derived from LRP ?
No. NETISR is
Harti Brandt wrote:
> You need to lock when reading if you insist on consistent data. Even a
> simple read may be non-atomic (this should be the case for 64bit
> operations on all our platforms). So you need to do
>
> mtx_lock(&foo_mtx);
> bar = foo;
> mtx_unlock(&foo_mtx);
>
> if foo is a dataty
Frank Mayhar wrote:
> The other thing is that the unlocked reads about which I assume Jeffrey
> Hsu was speaking can only be used in very specific cases, where one has
> control over both the write and the read. If you have to handle unmodified
> third-party modules, you have no choice but to do l
Peter Bozarov wrote:
[ ... ]
> What I can't seem to figure out is how to flush out the
> "stale" mbufs/clusters. I can close down all network
> interfaces, and kill/restart most of the processes that I
> presume use up the mbufs. At a given point, there can't
> possibly be any processes that are ho
Wilko Bulte wrote:
> On Tue, Oct 14, 2003 at 10:44:14PM +0200, Oldach, Helge wrote:
> > From: Richard Tobin [mailto:[EMAIL PROTECTED]
> > > > Ok, GEOM Gate is ready for testing.
> > > > For those who don't know what it is, they can read README:
> > >
> > > Aaargh! It's the return of nd(4) from Sun
Lev Walkin wrote:
> One of the most comprehensive sites about that problem is:
>
> http://www.kegel.com/c10k.html
That's about scaling to a large number of connections, not about
kqueue() vs. select performance.
The biggest problem with a large number of connections, at least
as far as FreeBSD i
Ted Unangst wrote:
> On Fri, 24 Oct 2003, Michel TALON wrote:
> > What is more interesting is to look at the actual benchmark results in
> > http://bulk.fefe.de/scalability/
> > in particular the section about mmap benchmarks, the only one where
> > OpenBSD shines. However as soon as touching pages
John-Mark Gurney wrote:
> Wes Peters wrote this message on Thu, Oct 23, 2003 at 01:43 -0700:
> > Kip Macy, other DragonFlyBSD developers, and anyone else wishing to
> > contribute are invited to join and participate in the open FreeBSD mail
> > lists, sharing code, design information, research and
Robert Watson wrote:
> On Sat, 25 Oct 2003, Matthew Dillon wrote:
> > It's a lot easier lockup path then the direction 5.x is going, and
> > a whole lot more maintainable IMHO because most of the coding doesn't
> > have to worry about mutexes or LORs or anything like that.
>
> You stil
Leo Bicknell wrote:
> Dan Langille wrote:
> > Any suggestions?
>
> Here's a slightly backwards concept.
>
> We're all familar with how you can open a file, remove it from the
> directory, and not have it "go away" until the application closes
> it. Well, extend those semantics to the namespace.
"Vinod R. Kashyap" wrote:
> I have this huge data structure in the data segment of my scsi driver. This
> data structure is initialized at driver build time, and is used only during
> driver
> initialization. I am trying to find out if I can free-up the memory it
> occupies,
> once I am done with
Christopher Vance wrote:
> You can already mark a fd 'close on exec'.
>
> May I suggest a different feature: the ability to mark an open file
> (not just its fd) 'remove on close', with permission checked at mark
> time rather than close time (this status forgotten if not permitted
> when set) and
andi payn wrote:
> As far as I can tell, FreeBSD doesn't have anything equivalent to
> linux's O_NOACCESS (which is not in any of the standard headers, but
> it's equal to O_WRONLY | O_RDWR, or O_ACCMODE). In linux, this can be
> used to say, "give me an fd for this file, but don't try to open it f
andi payn wrote:
> First, let me mention that I'm not nearly as experienced coding for *BSD
> as for linux, so I may ask some stupid questions.
>
> I've been looking at the fam port, and this has brought up a whole slew
> of questions. I'm not sure if all of them are appropriate to this list,
> bu
Nielsen wrote:
> Christopher Vance wrote:
> > May I suggest a different feature: the ability to mark an open file
> > (not just its fd) 'remove on close', with permission checked at mark
> > time rather than close time (this status forgotten if not permitted
> > when set) and the unlink actually do
andi payn wrote:
> Now hold on. The standard (by which I you mean POSIX? or one of the UNIX
> standards?) doesn't say that you can't have an additional flag called
> O_NOACCESS with whatever value and meaning you want.
A strictly conforming implementation can not expose things into
the namespace t
"M. Warner Losh" wrote:
> Rewind units on tape drives? If there's no access check done, and I
> open the rewind unit as joe-smoe? The close code is what does the
> rewind, and you don't have enough knowledge to know if the tape was
> opened r/w there.
Which brings up the idea of passing fp->fd_f
"C. Kukulies" wrote:
> I installed the spambouncer.org procmail script and before I was switching
> the behaviour from SILENT to COMPLAIN I took a look at my spam.incoming folder
> and found a lot of messages from freebsd-bugs and freebsd-mobile in there.
>
> Both lists are not directed to folders
Rod Person wrote:
> On Thursday 06 November 2003 09:09 am, It was written:
> > If you futs with getting Kylix to run under FreeBSD, don't forget the
> > special glibc requirements that some versions of Kylix have. Maybe you
> > should probably simply replace the entire /compat userland with the
> >
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 tha
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 t
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]
w
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 t
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 [E
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
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
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:
>
> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.
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
> >
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;
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
licen
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
>
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 o
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 co
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:
Pag
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 i
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 "unsu
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 thi
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 impro
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 tha
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
> authentic
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 deliver
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 thi
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 sho
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 t
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
Matthew Dillon wrote:
> :Cap the window size via the driver. This will probably require
> :another attribute on all drivers, indicating "max allowable window
> :size" ("0" could mean "any", and be used as the default so that we
> :don't end up flaking out someone talking to Mars).
>
> It won
Matthew Dillon wrote:
> Terry, I don't think you quite understand the problem. From the server's
> point of view NOTHING IS WRONG. Any non-USB-ethernet client would have
> no problem whatsoever with the large number of small packets that the
> server is sending, nor can the serve
Matthew Dillon wrote:
>
> Terry, I give up. Maybe if you actually tried to go in and fix it
> you would see what I'm talking about. For your information:
I don't have a USB/Ethernet adapter.
> * Julian's work has nothing to do with this particular problem. It
> has to do w
"Louis A. Mamakos" wrote:
>
> An underlying issue here is why applications decide to set TCP_NODELAY
> options on sockets, rather than just letting Nagle's algorithm do
> the right thing. I recall some handwaving about this in the X server
> some years ago to make mouse movements "smoother".
OK
Matthew Dillon wrote:
> Yes, you are correct. There is no real reason for ssh to set
> TCP_NODELAY on FreeBSD and, in fact, I believe it didn't used to.
> We should just turn it off.
FWIW, I agree that it should not be set. Setting socket options
has the unfortunate side effect of g
"Louis A. Mamakos" wrote:
>
> Disabling Nagle's algorithm for no good reason has very poor
> scaling behavior. This is what happens when TCP_NODELAY is
> enabled on a socket.
Disabling Nagle's algorithm for a good reason would still
result in the observed failure, however.
> If you look at t
"M. Warner Losh" wrote:
> In message: <[EMAIL PROTECTED]>
> Matthew Dillon <[EMAIL PROTECTED]> writes:
> : I think that has been fixed. Try it. It doesn't lag for me. The
> : turn-around echo of the keystroke should be pushed out instantly.
>
> Yes. Keep in mind that you o
Rafter Man wrote:
> [ ... ] but now I have one more question.
> From the 27/12 too the 29/12 I was at the CCC congress and attended
> a lecture called "Unix Redesigned". It was Neal H Walfield who talked
> about The Hurd:
[ ... ]
> So my question is: Will FreeBSD take a good look at the Hurd?
Y
Terry Lambert wrote:
[ ... ]
PS: See also:
http://www.eros-os.org/
http://icl.cs.utk.edu/publications/tech_reports/2000/ut-cs-00-445.pdf
http://www2.tunes.org/Review/OSes.html
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers&qu
"Rogier R. Mulhuijzen" wrote:
> At 11:42 1-1-2002 -0500, [EMAIL PROTECTED] wrote:
> >Just note that "no buffers" often means that the queue is full, not that you
> >are out of system buffers. You may be chasing a ghost.
>
> Well a queue should be cleaned shouldn't it? The mount_smbfs fails even
Steve Shorter wrote:
> I need an NFS server with 4G ram. When I boot a 4.5-PRE kernel
> it panics during the boot process, not always at the same place though.
> My first instinct is bad hardware because of the lack of consistency
> in panic location, however I was wondering if there were
Steve Shorter wrote:
> > You really need to change the allocation of swap page descriptors
> > in /sys/i386/machdep.c (among other things).
>
> Is this a trivial change? I don't know much about
> FreeBSD kernel internals but can edit source with some guidance OR
> can these changes be eff
701 - 800 of 1733 matches
Mail list logo
