t of government,
:truth can stand by itself." -Thomas Jefferson
:
What kernel version are you running?
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
T
for many
years. You can create filesystems and files up to 2TB in size in -stable
and it will be virtually unlimited in -current.
-Matt
Matthew Dillon
<[EMAIL PROTEC
:...
:>
:> Up to four, so then the theoretical limit for swap is 8TB?
:
:I hope not, since I have 6 of 'em. 4's just the default.
:
:
:> Do these management structures grow as swap grows, or do they only
:> change as the utilization increases?
:
:I believe they're pre-allocated, so it's the siz
Negative block numbers are used by UFS to represent the indirect blocks
associated with a file, while positive block numbers represent the
contents of the file.
These are logical block numbers, which are fragment-sized (1K typically).
So, 2^31 x 1K = 2TB.
Physical block n
:
:On Sat, Jul 06, 2002 at 04:42:22PM -0700, Matthew Dillon wrote:
:> Negative block numbers are used by UFS to represent the indirect blocks
:> associated with a file, while positive block numbers represent the
:> contents of the file.
:
:I never saw any negative block numb
I think that's the only 1TB vs 2TB issue.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
have it
all be useable by the system.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
:
:One of my FreeBSD development boxes had a hernia last week when it lost
:power while writing to disk. The drive wrote out garbage to a track.
:
:I want to reformat the drive, (low level) but the bios doesn't have any
:support to do this (In the past That is how I did this).
:The machiine has 1
:> > Julian got struck by lightning; perhaps he will now stick to disks
:> > with built-in lightning rods (e.g. not succeptible to this failure),
:> > e.g. SCSI.
:>
:> This is an urban ledgend..
:
:No - it's SCSI Specs.
:A SCSI Disk is required to savely finish the started sector even
:on powerl
age?
:
:> Crash dumps good.
:
:I beg to differ. ;-)
You only need as much as physical ram. e.g. 1G of ram, 1G on the
dump device (which can be the swap partition).
-Matt
Matthew Dillon
the size of physical memory.
:
:So I guess either you or the manpage is wrong.
:
:--
:
:Erik Trulsson
:[EMAIL PROTECTED]
The manual page is wrong. I'll fix it.
-Matt
that the OS is able to fill up the CDRs
pipelines. Once the pipelines are full things should work ok assuming
the CDs do SCSI disconnection properly to allow for parallelism.
I'm somewhat interested in knowing that this concept actually works :-)
ks for the help,
:
:Keith
Wow, that's excellent news Keith! I'm amazed that you were able to get
it to work so well with such an old box.
-Matt
Matthew Dillon
r a
kilobyte should be reviewed.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
:Good Morning,
:
:I would suggest that since we have an VM implementation that works,
:that the answer to y
ry to reduce load effects
on the system.
* The swap device being removed can now be closed and the related
swap device index marked free.
-Matt
Matthew Dillon
her swap to
take care of the data.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
We are not going to be doing any sort of weighting. It's an idea whos
time has come... and gone again. It might have been useful 8 years ago
but it is not useful today.
Also, please note that it is not possible to reverse-lookup a swap bitmap
block and get the VM object / pa
aboratories
You could create a port. e.g. 'senddevstat', which pops the person
into vi with a template and runs it through a checker when one
saves and quits, then asks whether to send it or not.
-Matt
lasting harm
the onus would be on the people with objections to prove it otherwise.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PR
Wow. I'm flattered. Everyone so far thinks 200ms will be ok!
Its up to Jonathan Lemon now. Jonathan, if you sign off on 200ms
for the MFC I'll go with it.
-Matt
Matt
:
:On Tue, 9 Jul 2002, Matthew Dillon wrote:
:>
:> There is no multi-target command that I know of. You are absolutely
:> correct in your bandwidth calculations... a SCSI bus should have no
:> problem at all duping the data 8 times to each of 8 CDR's, and the
am can mmap() before it runs out of VM.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Well, I'm back from vacation. I see nobody in the general group has
commented much on my bandwidth delay product code. A couple of people
have corresponded with me in email and generally the response is
positive.
Since this code must be enabled via a sysctl I feel it is saf
/* sequence number being timed */
:>
:> +int t_bw_rtttime; /* used for bandwidth calculation */
:
:Does this need to be signed?
I think you meant unsigned. No, it doesn't need to be unsigned. Hmm.
though it's possible rollover wi
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
lead opens a lot of doors.
HiC'p.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
metric tons of shit in his front yard.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers&q
g calculations. As long as people understand
this problem I believe the format is reasonable.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
(Matt's summary of sys
:> struct timeval64 {
:> time64_ttv_sec;
:> int64_t tv_frac;/* N/2^63 fractional */
:> };
:
:We have this one already, and it's called bintime, except that it
:correctly uses N/2^64 fractional the way binary computers prefer it.
:
:--
:
:>
:>All right, I'll amend the proposal to use 2^64. the fractional
:>element will be unsigned, the tv_sec will remain signed.
:
:That is exactly how bintime is defined :-)
:
: struct bintime {
: time_t sec;
: uint64_t frac;
: };
:
:If I had a int1
sort of solution.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
:Also, hackers@ is really not the place for this.
:
:Cheers,
:-Peter
:--
:Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTEC
My original proposal, before this one, was to create a separate
ABI for all the new calls, which also means creating a duplicate
set of libraries. I'm still game to do that -- it could be controlled
by a make.conf variable and selectable via a compiler option.
If we maintain
:Well, one thing that I would not be against is a clean divorce of the
:syscall layer and libc. That then gives us the freedom to implement
:alternative API selections etc at compile time pretty easily.
:
:I just really do not want to see this sort of thing turning up:
:
: time_t foo = time(0)
Oops, let me clarify what I mean by 'duplicate libraries'. I do
*NOT* mean duping the source code, I simply mean duping the
compile run in the buildworld, one for --unix32, one for --unix64,
for 32 bit platforms. 64 bit platforms would require no library
duplication at all (
hole point. You and others may like to do wholely working prototypes
in P4 and then smash the whole thing into -current but that isn't how
I work. So, no, I am not going to go about it that way.
-Matt
:
:Matthew Dillon wrote:
:> Well, then what we want is a new syscall vector, duplicate libraries,
:> and a compiler option, and leave all the function names the same
:> (which means no bintime but allows us to retain everything else).
:> -current would release sup
e_activate(m);
:+ vm_page_dirty(m);
:+ vm_page_wakeup(m);
:+ vm_page_unlock_queues();
:+ return 1;
:+ }
:+
:+ vm_object_pip_add(object, 1);
I think you may want to do the pip_add before calling vm_page_grab().
may need to
wait for other paging on the object (the pip count) to go to
zero. I will review that code more carefully in a little bit
and give you a definitive answer.
-Matt
Matthew Dillon
hrough to retry */
} else if (swap->swb_count <= 0) {
free the swap block
*pswap = swap->swb_hnext;
}
}
-Matt
Matthew Dillon
<[EMAIL
t works with or without
softupdates.
:Noatime won't help much in your examples either. It only buys you a lot
:if the data is spread over a large number of files.
-Matt
Matthew Dillon
:Matthew Dillon <[EMAIL PROTECTED]> wrote:
: >
: > atime/mtime/ctime updates will collect in the in-memory inode
: > and only be written to disk when the filesystem sync occurs once
: > every 30-60 seconds or so. This is how it works with or without
: > so
te swap you are
trying to free.
I think you may be ok.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscri
:..
:uhub1: 2 ports with 2 removable, self powered
:umass0: Sony USB Memory Stick Slot, rev 1.10/1.80, addr 2
:pci0: (vendor=0x8086, dev=0x2445) at 31.5 irq 9
:pci0: (vendor=0x8086, dev=0x2446) at 31.6 irq 9
:eisa0:
:
:Fatal trap 12: page fault while in kernel mode
:fault virtual address = 0x0
Oh, also, just a general note to people. These bug reports are great,
it tells us that something went wrong, but it would be nice if they
were a little more complete :-) For example, it wasn't until the 20th
posting in this and the similar other kernel panic thread on -hackers
nless you
:can see an obvious flaw in my approach.
I can probably deal with that post-commit. Lets ignore it for now.
The main goal at the moment should be robustness.
:BTW, thanks for all of your help!
-Matt
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
:No, I've tested it extensively, and I haven't been able to
:reproduce the problem since I updated my sources. (It was hard to
:reproduce beforehand.) I did two more runs with one
:Hi folks,
:
:I noticed that FreeBSD buf/bio subsystem has one very annoying problem
:- once the write request is ejected into it, and write operation
:failed, there seemingly no way valid to tell the layer to drop the
:buffer. Instead, it retries the attempt over and over again, until
:reboot, eve
:> :
:> :There is a very easy way to trigger the problem: insert blank floppy
:> :...
:>
:> Your patch looks slightly incomplete to me, but the concept is reasonable.
:> The BIO_NORETRY test that sets B_INVAL should probably be done in
:> brelse(), not in bufwait(). It is the code in
:
:Shouldn't the fact that the signal is in a while loop keep the 5 volt
:signal going? Isn't the parallel port being blasted with the
:value 255 over and over again?
:
:The serial port will not fulfill what i am ultimately trying to achive. I
:am trying to have the parallel port to control 8 rel
:
:Matthew Dillon wrote:
:> Uh guys. Parallel port digital outputs do not generally have a whole
:> lot of drive. I really doubt a parallel port output could drive a
:> relay.
:
:Depends on the amperage the relay draws. 8-).
:
:I used to use the paralell port output t
ce.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
alone will not stop a big static shock,
only a Zener diode is fast enough to do that. An external series
resistor is there strictly for current limiting purposes.
-Matt
Matt
of this for so_linger, so we could make it unsigned, but I
don't see any pressing need to do so. The range check would need
to be in there in either case.
Can I go ahead and commit it?
-Matt
Ma
I've been pulling my hair out all night trying to figure out how
the hell the VM86 code is able to issue an int 0x15 to the BIOS.
I can't find where it gets the interrupt descriptor table entry
for int 0x15. My assumption is that it copies it from the idt
supplied by the BIOS b
:
:
:On 08-Nov-2002 Matthew Dillon wrote:
:> I've been pulling my hair out all night trying to figure out how
:> the hell the VM86 code is able to issue an int 0x15 to the BIOS.
:> I can't find where it gets the interrupt descriptor table entry
:> for int 0
ables that I forgot that they can be ignored
in virtual 8086 mode. I dunno in regards to the IOPL, I'll look into
that, but you've definitely hit the nail on the head. Thanks a
bunch!
-Matt
INTn calls
itself, but it would be a lot cleaner.
Again, thanks for your help Luoqi.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
:...
:mode idt vector. Dependi
I was going to wait till 5.0 released first but I could do it now
if you want.
-Matt
:
:Matthew Dillon wrote:
:> I think your patch is fine as is, Mike! Good find! Even though
:> so_linger cannot be negative, it is often convenient
sand ways to do it.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
:> is certainly a lot safer if the stuff behind the mount is mostly
:> static.
:
:null mounts, in -stable at least, are broken for this purpose. on
:connection, sshd revoke()s some device- its pty, i assume, and when this
:hits the nullfs layer a null pointer is dereferenced. if i had vf
:> Try using null mounts. The warning is in there because making the
:> null mount code work is a real hack and the authors aren't entirely
:> sure that everything's gotten covered. That said, use of a null mount
:> is certainly a lot safer if the stuff behind the mount is mostly
Hmm. While tracking down a null mount issue I think I might have
come across a potentially serious problem with jail. It seems to
me that it would be possible for someone inside a jailed environment
to 'steal' pty's, tty's, or the tty side of a pty that is being
used from with
:
:In message <[EMAIL PROTECTED]>, Matthew Dillon w
:rites:
:>Hmm. While tracking down a null mount issue I think I might have
:>come across a potentially serious problem with jail. It seems to
:>me that it would be possible for someone inside a jailed environment
. This way if a jail eats all the ptys the sysadmin
can still ssh in.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
:>exhaust all available ptys?
:
:No.
:
:--
:Pou
:> I'm fairly sure the VM issues were fixed when VOP_GETVOBJECT was
:> added. A file accessed via a null mount will have the same VM object
:> as the file in the original filesystem. I'm not 100% sure about
:> that, I wasn't the one who did it, but I seem to recall it being
:>
:>
:> It should be calling VOP_BMAP through the VP stored in the VM
:> object, which will be the underlying file, not the nullfs.
:
:Probably, but it's not doing that. The NULLFS implement VOP_BMAP
:as vop_eopnotsupp; it doesn't fall through. Even if it did fall
:through, the vfs_defaul
Cameron and I have been working through some of the more blatent bugs.
Here is an intermediate patch for -stable, for both unionfs and nullfs.
There are still plenty of bugs left but this patch should fix the
major issues with devices.
Basically what is going on is that speci
:Matthew Dillon wrote:
:> So this patch is a hack. It returns special devices directly whenever
:> possible but must still synthesize temporary vnodes for them for
:> RENAME and DELETE operations. But short of rewriting a big chunk of
:> the device tracking infrastr
tend it out and mini-libc (as a separate
entity) also extend it out. That would reduce code duplication
considerably yet still allow the libraries to focus on the
particular functions they were designed for.
, and malloc
using my zalloc core.
The only thing libstand seems to be missing is a stdio equivalent
and sn*printf().
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To
libc's stdio if it isn't too big).
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
I have sucessfully created a mini-C-like library and
compiled /bin/sleep against it. (This is in stable,
by the way, so its still a bit bigger then it needs to be).
My minic library is:
apollo:/usr/src/lib/libminic# ls -la
total 30
drwxr-xr-x 2 root wheel 512 Nov 15 02:17 .
drwx
to work with a few more bin/ programs and
translate it to -current.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "u
:Will the knobs allow one to link /bin and /sbin against full blown
:libc? That would be nice as we can then start using pam and user
:management in / with dynamic modules (finally!).
:
:--
:-Alfred Perlstein [[EMAIL PROTECTED]]
I think that should be a goal. I think something like this:
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
RCS file: lib/libminic/asprintf.c
diff -N lib/libminic/asprintf.c
--- /dev/null 1 Jan 1970 00:00:00 -
+++ lib/libminic/asprintf.c 15 Nov 2002 20:27:11 -0000
@@ -0,0 +1,23 @@
+/*
+ * ASPRINTF.C
+ *
+ * (c)copyright 1993-94, 2002 Matthew Dillon, All
d mmap() the library from the kernel image
directly.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
bedded system but just as
significantly NON-useful in a normal system.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "
7;t know enough about the issue though I don't see
why it would be the case. the Dynamic link loader ought to work
either way.
-Matt
Matthew Dillon
<[EMAI
ouldn't be
discounted either.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
is lifted and I would be happy to do the work.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
:
:Alright, I've never tested this on -CURRENT though... I don't see
:
:You don't have anything to commit :-) mmap2 already exists in -CURRENT,
:it's only missing in -STABLE. So I'd think you probably don't have to
:worry about it.
:
:Ken
Ah, excellent. Then it only needs to go into -stable.
-Matt
To Unsubscri
In C for the IA32, EAX, ECX, and EDX are scratch registers. All other
registers must be saved and restored by the procedure.
Also keep in mind that the return value of a procedure is placed in
eax. If the return value is a 64 bit value, it is placed in eax and
edx.
:> function A calls function B which uses ecx as a loop index. The bad part is
:function B never
:> saves/restores the value of ecx and function A starts dereferencing garbage.
:>
:> An informal sampling of my driver seems to indicate that ebx gets
:> pushed/poped at entry/exit but ecx and edx do
also brings up the possibility that we could integrate setattr-like
functions into the MAC layer, which is already extensible, yes?
-Matt
Matthew Dillon
<[EMAIL PROT
And, I will also add, in regards to using the stat structure for
setattr(), that it creates a serious portability problem as well as
a serious forward and reverse compatibility problem. Which fields
in the stat structure are going to be ignored by the syscall and
which are no
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
nning the blind proxies he abuses to post, either.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
: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
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.
:Yes, we need to embrace the trolls and stop marginalizing them. The
:Troll-man has been downtrodden for far too long, it is time for him to
:step into the light of society and be accepted for what he is...assuming
:they don't shrivel up and die in the light. I don't know about you, but
:tha
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
Incidentally, does anybody know the status of FreeBSD/bluetooth?
I was thinking about trying it, seems cute enough. Looking in the
/dev/bluetooth directory though, I'm not sure its all there.. I'd
have to use a pcmcia card myself, but if the command stack were
available, maybe I could work out the
In soviet Russia... Dillon trolls YOU!!!
_
Get your own free tiggerfan.com email address!!
DisneySites!! - http://www.disneysites.com/webmail/tiggerfan
_
Select your own custom
:Hi,
:
:It seems that kern/32672 is not fixed yet on FreeBSD 4.5-STABLE.
:
:System 4Gb RAM, 4x700MHz
:
:When the system is not using all RAM, the FFS node memory grows up to a
:limit of 102400K which leads to a system deadlocking.
Well, there was some further work done to the vnode reclamation
returned. Am
I missing something?
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
:I think there can be a problem if we allow rfork without
:either RFCFDG or RFFDG and RF
s appreciated.
:
:--
:Zhihui Zhang. Please visit http://www.freebsd.org
:--
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubs
Here's the basic problem: The kernel is currently designed for
single-threaded operation plus interrupt handling. A piece of code
in the kernel can temporarily disable certain interrupts with the
spl*() codes to cover situations where a race on some system resource
might occ
a perfect test case for us because it will be
fairly easy to port and fairly easy to measure performance under load.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To U
801 - 900 of 1441 matches
Mail list logo
