On Wed, 12 Dec 2001, Matthew Dillon wrote:
> :I suppose while were on the topic..
> :
> :Are there any hidden secrets to eeking out more performance from the BSD
> :NFS client (other than version types and the normal fstab tweaks).
> :
> :Im the CS Labs manager at NetApp..and Im always trying to
:I suppose while were on the topic..
:
:Are there any hidden secrets to eeking out more performance from the BSD
:NFS client (other than version types and the normal fstab tweaks).
:
:Im the CS Labs manager at NetApp..and Im always trying to store away a
:secret here or there when someone comes t
Very cool. Good job!
-DG
David Greenman
Co-founder, The FreeBSD Project - http://www.freebsd.org
President, TeraSolutions, Inc. - http://www.terasolutions.com
Pave the road of life with opportunities.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the bo
:Does the softupdates fix affect normal ffs operations as well?
:
:Mike "Silby" Silbersack
Yes, we believe so. It's a bug in ftruncate()'s interaction
with softupdates.
-Matt
Matthew Dillon
I suppose while were on the topic..
Are there any hidden secrets to eeking out more performance from the BSD
NFS client (other than version types and the normal fstab tweaks).
Im the CS Labs manager at NetApp..and Im always trying to store away a
secret here or there when someone comes to me wit
On Wed, 12 Dec 2001, Matthew Dillon wrote:
>
> :
> :Are any of these client-side performance upgrades as well as bug fixes?
>
> No, just bug fixes. The softupdates bug fix is server-side. All
> the other bug fixes are client side (so far).
>
>
:
:Are any of these client-side performance upgrades as well as bug fixes?
No, just bug fixes. The softupdates bug fix is server-side. All
the other bug fixes are client side (so far).
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED
Hi Folks,
This is the first call for participation in the Works In Progress
session at BSD Con '02 in San Francisco. Works In Progress talks
are 5 to 10 minute presentations of the work you're doing with BSD
that would be of interest to other people.
Please send a subject, short
Are any of these client-side performance upgrades as well as bug fixes?
On Wed, 12 Dec 2001, Matthew Dillon wrote:
> Ok, here is the latest patch for -stable. Note that Kirk comitted a
> slightly modified version of the softupdates fix to -current already
> (the VOP_FSYNC stuff), wh
Ok, here is the latest patch for -stable. Note that Kirk comitted a
slightly modified version of the softupdates fix to -current already
(the VOP_FSYNC stuff), which I will be MFCing in 3 days.
This still doesn't fix all the problems the nfstest program that Jordan
posted fin
> To be clear, what exactly are you doing?
>
> It sounds like you're exporting something from freebsd, mounting it on OSX
> and running this tool on OSX against the filesystem exported from freebsd ?
>
> If so, What mount options? NFSv2 or v3?
That is correct. As to the NFS options used, I ho
Hello,
I am working on a FreeBSD device driver for a custom
PCI bus device developed by my company. The PCI card
has large amounts on memory on it and we are using
bus master DMA to get data in and out of memory.
The proceedure that I am using is as follows:
A.1. The DMA controller on our devic
Title: Lighthouse in the Sunset
Hi There,
My name is John.
I am a simple man living in North Carolina.
I have learned how to make a living on the net.
I am willing to teach you to do the same, in simple easy to understand lessons.
I will work with you an
I found a second bug... nfs truncation code race.
I've enclosed both patches below. NFS truncation race first, softupdates
bug second. The patches are against -stable.
There are still more bugs... the nfstest code is seeing data corruption
on read. It looks like another t
Jordan Hubbard wrote:
> > I should point out that FSX can be used against any filesystem, and
> > that there are reports locally (at Apple) that it's great for killing
> > FreeBSD machines. I wasn't able to reproduce this when I tried, but I
> > may not have let it run long enough.
>
> Oh, it bl
On Wednesday, 12 December 2001 at 1:43:10 -0800, Hiten Pandya wrote:
> Hi,
>
> as i said also before, my intentions were never to cause havoc on
> the mailing list. :-)
>
> In simple terms, what i am saying is, the people who would like to
> port the JFS file system, should put a +1 in their next
:
:> I should point out that FSX can be used against any filesystem, and
:> that there are reports locally (at Apple) that it's great for killing
:> FreeBSD machines. I wasn't able to reproduce this when I tried, but I
:> may not have let it run long enough.
:
:Oh, it blows freebsd.apple.com rig
> I should point out that FSX can be used against any filesystem, and
> that there are reports locally (at Apple) that it's great for killing
> FreeBSD machines. I wasn't able to reproduce this when I tried, but I
> may not have let it run long enough.
Oh, it blows freebsd.apple.com right out of
:
:
:I should point out that FSX can be used against any filesystem, and
:that there are reports locally (at Apple) that it's great for killing
:FreeBSD machines. I wasn't able to reproduce this when I tried, but I
:may not have let it run long enough.
Well, I already found and tracked down
I should point out that FSX can be used against any filesystem, and
that there are reports locally (at Apple) that it's great for killing
FreeBSD machines. I wasn't able to reproduce this when I tried, but I
may not have let it run long enough.
> Oooh. Very cool! I'll start messing with i
>
> > You should look at recent PCI revisions, however, and the MSI
> > (message-signalled interrupt) mechanism which, if implemented widely,
> > will solve at least some of the major problems with PCI and interrupts.
>
> Thanks for the pointer; I haven't been following PCI standards
> recently,
also look at (in current
only!) /usr/share/examples/drivers/make_device_driver.sh
is makes a driver with ISA, and PCI-based interfaces.
On Wed, 12 Dec 2001, Chuck T. wrote:
> I'm trying to write an ISA device driver from scratch and I'm also trying to
> make it a kernel loadable to make my de
> The only thing I get is a math exception because "closeprob" is zero
> since no -c option was given.
>
> Can you provide some sample parameters please ?
Hmmm, how strange, now that I look at the code it's obvious that a
divide by zero will occur with a zero closeprob and the docs state the
def
Jos Backus <[EMAIL PROTECTED]> wrote:
> Is this PR-worthy? I am seeing this in both -stable and -current. The lftp
> author claims it's our bug, not his.
>
> > It seems to me that sscanf on FreeBSD does not correctly handle long
> > long type (%lld). There is another similar report, the reporter
In message <[EMAIL PROTECTED]>, Jordan Hubbard writ
es:
>Usage:
> cc fsx.c -o fsx
> ./fsx /some/nfs/mounted/scratchfile
> [ ** kaboom! ** ]
The only thing I get is a math exception because "closeprob" is zero
since no -c option was given.
Can you provide some sample parameters
Title: SENSITIVE MESSAGE
Linus Torvalds,
this message is time sensitive. Contact us immediately!
We
know more about
you than you may think!
Linus Torvalds,
this notice is for
In message <[EMAIL PROTECTED]> Matthew Dillon writes:
: Oooh. Very cool! I'll start messing with it (oops, that's going to
: make both Paul and Alfred annoyed with me!)
Well, I can understand you not wanting to upset Paul, but anything
that annoys Alfred can't be all bad, can it :-)
Wa
Oooh. Very cool! I'll start messing with it (oops, that's going to
make both Paul and Alfred annoyed with me!)
-Matt
:It came up in a meeting today at Apple just how fragile the BSD NFS
:implementation was before significant work was put in to st
I'm trying to write an ISA device driver from scratch and I'm also trying to
make it a kernel loadable to make my debugging life easier. I started with
/usr/share/examples/kld/cdev and have modified it by adding the following:
static int
xxx_isa_probe(device_t dev)
{
int ret = ENXIO;
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
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
In message <[EMAIL PROTECTED]> Terry Lambert writes:
: How is setting a local register when an interrupt is triggered
: antithetical to such cards working? I know of several network
: cards where I've personally hacked on the driver that have such
: a register.
...
I was tired and confused when
> I never understood why the PCI-bus is not a interupt vector design.
The way the story goes, it wasn't until the last minute that the initial
PCI working group realised that they'd forgotten to do something about
interrupts, and so the gross hack that we're now stuck with was
implemented.
It
There's a mention in the FBSD hacking guide that a detach() routine
for a device driver can forcably close all open descriptors for
its device before it unloads.
How does one do this?
brad
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the mes
It came up in a meeting today at Apple just how fragile the BSD NFS
implementation was before significant work was put in to stabilizing it,
and in that discussion came up a little test tool written originally by
Avie Tevanian and subsequently improved by one of the folks here.
This tool basicall
On Wed, Dec 12, 2001 at 04:28:25PM +0200, Danny Braniss wrote:
>
> > I never understood why the PCI-bus is not a interupt vector design.
> >
> probably because it was DEC's idea ...
I thought it was Intel's idea?
--
| / o / /_ _ email: [EMAIL PROTECTED]
|/|/ / / /( (_) B
> I never understood why the PCI-bus is not a interupt vector design.
>
probably because it was DEC's idea ...
danny
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Wed, Dec 12, 2001 at 03:02:19AM -0800, Terry Lambert wrote:
> How is setting a local register when an interrupt is triggered
> antithetical to such cards working? I know of several network
> cards where I've personally hacked on the driver that have such
> a register.
>
> It's not possbile to
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 inter
Hi,
as i said also before, my intentions were never to
cause havoc on the mailing list. :-)
In simple terms, what i am saying is, the people who
would like to port the JFS file system, should put a
+1 in their next message and -1 if they dont like to
port JFS.
Then, i will count the votes, an
> In message <[EMAIL PROTECTED]> Danny Braniss writes:
> : Q: are all interrupt handlers for the shared irq called, or only the
> :'correct' one?
>
> You can't tell which card really interrupted. All of them are called.
>
> Warner
let me see if i can summarise:
1- irq are shared by
41 matches
Mail list logo
