On Jan 19, 2013, at 4:33 PM, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl
wrote:
to be enabled to get any speed-up from tagged commands. This was no
risk with SCSI drives, since the cache did not make the drives lye
i see no correlation between interface type and possibility of lying
Try adding the following to /boot/loader.conf and reboot:
hw.mpt.enable_sata_wc=1
The default value, -1, instructs the driver to leave the STA drives at their
configuration default. Often times this means that the MPT BIOS will turn off
the write cache on every system boot sequence. IT DOES
- Original Message -
From: Wojciech Puchar woj...@wojtek.tensor.gdynia.pl
To: Scott Long scott4l...@yahoo.com
Cc: Dieter BSD dieter...@gmail.com; freebsd-hackers@freebsd.org
freebsd-hackers@freebsd.org; gi...@freebsd.org gi...@freebsd.org;
sco...@freebsd.org sco...@freebsd.org; mja
On Jan 18, 2013, at 1:12 PM, Dieter BSD dieter...@gmail.com wrote:
It is inexcusable that FreeBSD defaults to leaving the write cache on
for SATA PATA drives.
This was completely driven by the need to satisfy idiotic benchmarkers,
tech writers, and system administrators. It was a huge deal
On Aug 2, 2012, at 12:23 AM, Kevin Oberman kob6...@gmail.com wrote:
Doug makes some good points.
No, he doesn't. He and Arnould being argumentative and accusatory where none
of that is warranted.
I used to run the devsummits, and we did tele-conference lines for remote
people to
Once the bio is put into the bioq from da_strategy, the CAM scheduler is
called. It may or may not wind up calling dastart right away; if the simq or
devq is frozen, or if the devq has been exhausted, then the io will be deferred
until later and the call stack will unwind back into g_down.
David Xu wrote:
Julian Elischer wrote:
David Xu wrote:
David Xu wrote:
Julian Elischer wrote:
depends on the hardware.
anyhow I was only saying it was possible, not necessarily
good or even useful.
I had done some works for thread private page shared by kernel
and userland when I was
Danny Braniss wrote:
Danny Braniss wrote:
it seems March 12 was a bit off :-)
it took some time, but I managed to close the gap:
189100 ok
189150 fails
I will continue tomorrow, but this should be helpful.
189150 is in the middle of a big string of related commits. Try
Danny Braniss wrote:
Danny Braniss wrote:
Danny Braniss wrote:
it seems March 12 was a bit off :-)
it took some time, but I managed to close the gap:
189100 ok
189150 fails
I will continue tomorrow, but this should be helpful.
189150 is in the middle of a big string of
Danny Braniss wrote:
it seems March 12 was a bit off :-)
it took some time, but I managed to close the gap:
189100 ok
189150 fails
I will continue tomorrow, but this should be helpful.
189150 is in the middle of a big string of related commits. Try
updating to the
Danny Braniss wrote:
Danny Braniss wrote:
at least for me :-)
[and sorry for the cross posting]
old (March 12 , i know need the svn rev number but...)
None of the commit activity on March 12 is jumping out at me as being
suspicious. However, you are now the second person who has told me
I've been talking about this for years. All I need is help with the VM
magic to create the page on fork. I also want two pages, one global
for gettimeofday (and any other global data we can think of) and one
per-process for static data like getpid/getgid.
Scott
Sergey Babkin wrote:
Robert Watson wrote:
On Fri, 27 Mar 2009, Scott Long wrote:
I've been talking about this for years. All I need is help with the
VM magic to create the page on fork. I also want two pages, one
global for gettimeofday (and any other global data we can think of)
and one per-process
Julian Elischer wrote:
Max Laier wrote:
On Thursday 05 February 2009 23:18:36 Oliver Fromme wrote:
I have posted detailed instructions on the FreeBSD wiki:
http://wiki.freebsd.org/OliverFromme/BootLoaderTest
Any kind of feedback is welcome.
quick test in qemu - works well. Very cool!
Oliver Fromme wrote:
Hello fellow hackers,
Some of you might remember that I'm working on graphics
support for our /boot/loader. Unfortunately, progress has
been rather slow because of non-FreeBSD-related activity.
Anyway, I have now prepared a tarball containing a loader
binary for public
Ed Schouten wrote:
Hello Theirry,
* Thierry Herbelot [EMAIL PROTECTED] wrote:
with the following patch on /sbin/init, I have two different behaviours
depending on the console type (on a i386/32 PC) :
- on a video console, I see the expected two messages,
- on a serial console, the messages
Pav Lucistnik wrote:
Andriy Gapon píše v čt 28. 02. 2008 v 10:33 +0200:
And while I have your attention, I have a related question.
I have produced a bunch of ISO9660 Level 3 / UDF hybrid media with
mkisofs, and when I mount the UDF part of them, the mount point (root
directory of media) have
Andriy Gapon wrote:
on 26/02/2008 21:23 Pav Lucistnik said the following:
Pav Lucistnik píše v út 05. 02. 2008 v 19:16 +0100:
Andriy Gapon píše v út 05. 02. 2008 v 16:40 +0200:
Yay, and can you fix the sequential read performance while you're at it?
Kthx!
this was almost trivial :-)
See the
Andriy Gapon wrote:
on 04/02/2008 22:07 Pav Lucistnik said the following:
Julian Elischer píše v po 04. 02. 2008 v 10:36 -0800:
Andriy Gapon wrote:
More on the problem with reading big directories on UDF.
You do realise that you have now made yourself the official
maintainer of the UDF file
Andriy Gapon wrote:
More on the problem with reading big directories on UDF.
First, some sleuthing. I came to believe that the problem is caused by
some larger change in vfs/vm/buf area. It seems that now VMIO is applied
to more vnode types than before. In particular it seems that now vnodes
Boris Samorodov wrote:
Hi!
Since nobody answered so far, here is my two cents. I'm not an expert
here so it's only my imho.
On Wed, 17 Oct 2007 22:52:49 +0400 Alexey Popov wrote:
interrupt total rate
irq6: fdc0 8 0
irq14:
Wilko Bulte wrote:
On Fri, Jan 12, 2007 at 09:31:04PM +0200, Danny Braniss wrote..
--s/l3CgOIzMHHjg/5
Content-Type: text/plain; charset=iso-8859-2
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Jan 09, 2007 at 09:06:46AM +0200, Danny Braniss wrote:
Hi,
Danny Braniss wrote:
I forget, does iSCSI have a concept of a flush_cache command, or the
equivalent of what parallel SCSI does with ordered tags?
not realy - or I can't find it. iSCSI is mainly and envelope for
scsi commands, so whatever the CAM does, it will pass it on.
There are some
Danny Braniss wrote:
hi,
I'm trying to finish up the iSCSI initiator,
and need some advice. To shutdown the initiator, I
need to:
1- close down the CAM-peripherals, (ie da)
2- empty up all pending iSCSI transactions
3- close the tcp connection
2 3 I can handle,
Wilko Bulte wrote:
On Wed, Jul 05, 2006 at 08:02:55PM -0500, Derrick T. Woolworth wrote..
Hello all,
Sorry for cross-posting, but these issues seem relevant for lists...
Has anyone had success with SATA300 controllers with FreeBSD 6.1? I've been
trying Promise and nVidia nForce4 and I'm not
Danny Braniss wrote:
Hi,
on a fairly new 6.1-stable, and probably before, once in a
blue moon, sendto return error 64 (EHOSTDOWN?). but the packet seems to have
been received by the target, since i get a response, and further more,
everything keeps on working.
what is error 64?
danny
Danny Braniss wrote:
Danny Braniss wrote:
Hi,
on a fairly new 6.1-stable, and probably before, once in a
blue moon, sendto return error 64 (EHOSTDOWN?). but the packet seems to have
been received by the target, since i get a response, and further more,
everything keeps on working.
M. Warner Losh wrote:
: THIRD
: Because the PCIE configure space is 4k long ,shall we change the
: #define PCI_REGMAX 255
: to facilitate the PCI express config R/W?
Maybe. Lemme investigate because PCIe changes this from a well known
constant for all pci busses, to a variable one...
william wallace wrote:
On 5/30/06, Scott Long [EMAIL PROTECTED] wrote:
M. Warner Losh wrote:
: THIRD
: Because the PCIE configure space is 4k long ,shall we change the
: #define PCI_REGMAX 255
: to facilitate the PCI express config R/W?
Maybe. Lemme investigate because PCIe changes
william wallace wrote:
[...]
MSI:
I've bantered around different suggestions for an API that will support
this. The basic thing that a driver needs from this is to know
exactly how many message interrupt vectors are available to it. It
can't just register vectors and handlers blindly since
[EMAIL PROTECTED] wrote:
Hi guys:
The attached file is the sample codes of my HBA driver. I make notes on the
place where the address transfer is needed. Please make comments if
possible.
Thanks a lot!
Hong
It looks like the primary question that you are asking in the code is
[EMAIL PROTECTED] wrote:
Hi guys:
To access sg_table in kernel address, I need to map the starting physical
address of a segment into a kernel address. As I know that, we can use
phystovirt()/bustovirt(), or kmap()/kmap_atomic() to map a bus/physical
address or a physical page into a
This would be awesome, please do it.
Scott
Benno Rice wrote:
One of the things that I found useful both in starting the PowerPC port
and in doing the XScale stuff I'm working on is making the SYSINIT stuff
done by mi_startup() verbose. This generally requires hacking your own
code into
Mike Jakubik wrote:
Jonathan Noack wrote:
The *entire* errata page was from 6.0; it was a mistake. This wasn't
some put on the rose-colored classes and gloss over major issues
thing. It was a long release cycle and something was forgotten. C'est
la vie. It's always a good idea to check
Andrey Simonenko wrote:
Greetings,
In my environment non-atomic updates of NFS export lists are not
acceptable. So, I decided to correct this problem. As the result
mountd, kern/vfs_export.c were completely rewritten, mount.h,
vfs_mount.c and nfs_srvsubs.c also got changes.
For details see
the release engineering activities for FreeBSD 6.1 including
The FreeBSD Foundation, FreeBSD Systems, Hewlett-Packard, Yahoo!,
Sentex Communications, and Copan Systems.
The release engineering team for 6.1-RELEASE includes:
Scott Long [EMAIL PROTECTED] Release Engineering,
Ken Smith [EMAIL
Erich Dollansky wrote:
Hi,
Eric Anderson wrote:
Erich Dollansky wrote:
Hi,
Eric Anderson wrote:
PID USERNAMETHR PRI NICE SIZERES STATE C TIME WCPU
COMMAND
11 root 1 171 52 0K 8K CPU1 0 0:00 99.02%
idle: cpu1
2653 root 1 1280
All,
I'm foregoing the formal pretty announcement for 6.1-RC2 because the
message needs to get out and I don't have an hour to spend on making it
look nice.
FreeBSD 6.1-RC2 is available for download. This is the last RC before
the release. Please test it to make sure that there have been no
Iantcho Vassilev wrote:
Hello guys,
in bsdnews.com i found this link http://kerneltrap.org/node/6506 and
particulary this:
I claim that Mach people (and apparently FreeBSD) are incompetent idiots.
Playing games with VM is bad. memory copies are _also_ bad, but quite
frankly, memory copies
Announcement
The FreeBSD Release Engineering Team is pleased to announce the
availability of FreeBSD 6.1-RC1. It is meant to be a refinement of the
6-STABLE, branch with few dramatic changes. A lot of bugfixes have been
made, some drivers have been updated, and some areas have
Nickolas wrote:
Hello All!
I'm porting a CPI card driver from linux to FreeBSD.
Some initialization routines require much time (~1-2 seconds).
Initialization of hardware should be done during opening device
special file. So, I need to switch thread context.
I'm doing it in such way:
Ceri Davies wrote:
On Fri, Apr 07, 2006 at 03:57:42PM -0700, Brooks Davis wrote:
On Fri, Apr 07, 2006 at 11:53:42PM +0100, Ceri Davies wrote:
I'm trying to configure a bootable image to be used in various situations
and on various (mostly unknown) hardware.
For the filesystem I can use
Mike Meyer wrote:
In [EMAIL PROTECTED], Scott Long [EMAIL PROTECTED] typed:
Well, the real question is why we force the details of driver names onto
users. Network and storage drivers are especially guilty of this, but
tty devices also are annoying.
Because Unix has always made
Mike Meyer wrote:
In [EMAIL PROTECTED], Scott Long [EMAIL PROTECTED] typed:
Please trim the text you are repling to.
Please, I'm tired of arbitrary email etiquette.
But where do you put the label on an ethernet interface?
mike
It sounds like your message is, don't be like Linux
Ceri Davies wrote:
On Sat, Apr 08, 2006 at 08:34:30AM -0600, Scott Long wrote:
On Fri, Apr 07, 2006 at 11:53:42PM +0100, Ceri Davies wrote:
For the filesystem I can use geom_label and /dev/ufs/UnlikelyString, but
I'd
also like to have it try to configure whatever interfaces the machine
Robert Huff wrote:
Sam Leffler writes:
OTOH we've done nothing with user application code and based on
the work I've seen done by netbsd there's plenty of stuff to be
fixed there.
When you say user application code, is this an alias for
ports or do you mean non-ported
Jacques Marneweck wrote:
Danny Braniss wrote:
Daichi GOTO wrote:
All folks have interests in improved unionfs should keep attentions
and ask how about merge? at every turn :)
OK. How about a merge?
I'd really like to see this in 6-STABLE.
Regards,
Jan Mikkelsen.
just a
Daichi GOTO wrote:
Jan Mikkelsen wrote:
Daichi GOTO wrote:
All folks have interests in improved unionfs should keep attentions
and ask how about merge? at every turn :)
OK. How about a merge?
I'd really like to see this in 6-STABLE.
Me too, but unfortunately it is difficult with some
John Baldwin wrote:
On Wednesday 15 March 2006 12:11, Rick C. Petty wrote:
On Wed, Mar 15, 2006 at 10:46:01AM -0500, John Baldwin wrote:
I'm using a USB keyboard, no PS/2. I've tried the hint to disable kbdmux,
I've tried with and without selecting the Boot w/ USB keyboard and the
machine
Announcement
The FreeBSD Release Engineering Team is pleased to announce the
availability of FreeBSD 6.1-BETA4 and FreeBSD 5.5-BETA4. Both FreeBSD
6.1 and FreeBSD 5.5 are meant to be a refinement of their respective
branches with few dramatic changes. A lot of bugfixes have been
Sorry, I accidentally sent out an incomplete draft. This announcement
is for BETA4, of course. Also, the note about VFS changes below should
stress that the changes were made for stability, not performance. Sorry
for the confusion.
Scott Long wrote:
Announcement
The FreeBSD
Aniruddha Bohra wrote:
On Thu, 2006-03-02 at 13:28 -0800, Kip Macy wrote:
-CURRENT runs on 3.0 as a domU. There is partial dom0 support. The
changes have not gone back into the mainline because xenbus is
extremely difficult to integrate cleanly. You can check on the state
of the xen3 branch in
Ashok Shrestha wrote:
VMWARE GSX was released recently for free.
[http://www.vmware.com/news/releases/server_beta.html]
Is anyone working on a port for this?
I've started on it, but I haven't made much progress yet.
Scott
___
Dave wrote:
Hello,
Some urgency on this issue!I've got a 10 gb ide drive that has
critical data on one of it's
partitions /dev/ad1e. This drive was originally gmirrored in
another box it worked fine, it was the master drive. Now i've
installed this drive as a slave in another 6.0 box,
Announcement
The FreeBSD Release Engineering Team is pleased to announce the
availability of FreeBSD 6.1-BETA2 and FreeBSD 5.5-BETA2. Both FreeBSD
6.1 and FreeBSD 5.5 are meant to be a refinement of their respective
branches with few dramatic changes. A lot of bugfixes have been
Nate Nielsen wrote:
I'm developing for small embedded systems, and I'm looking into the
possibility of dumping a kernel core dump to a USB memory stick (umass
driver). It currently doesn't work (see below), but I'm interested in
fixing it.
Yes, I know it'll be slow. It's probably also a
Announcement
The FreeBSD Release Engineering Team is pleased to announce the
beginning of both the FreeBSD 6.1 and FreeBSD 5.5 release cycles with
the availability of FreeBSD 6.1-BETA1 and FreeBSD 5.5-BETA1
Both FreeBSD 6.1 and FreeBSD 5.5 are meant to be a refinement of their
John Baldwin wrote:
On Tuesday 24 January 2006 19:34, Craig Boston wrote:
On Tue, Jan 24, 2006 at 10:43:49AM -0500, John Baldwin wrote:
What if you do a read of the lapic before the write? Maybe doing 'x =
lapic-eoi; lapic-eoi = 0;'?
Reading the lapic before the write has no effect.
Pranav Peshwe wrote:
Hello,
When a kthread is created using the kthread_create (9)
function, i found out that a new instance of struct proc is created
and allocated for the thread just as in case of a creation of a new
process.Also, the thread is assigned a pid as in the case of a
Craig Boston wrote:
After trying everything I could think of to do to the I/O APIC code and
coming up empty, tonight I went back to the local APIC. I had
previously ruled it out since the lapic timer interrupt continued to
work fine even when the others stopped. However, adding some DELAY(1)
Daniel Eischen wrote:
On Tue, 3 Jan 2006, John Baldwin wrote:
On Sunday 01 January 2006 02:21 am, prime wrote:
Hi hackers,
I have an idea about remove the kernel option MUTEX_WAKE_ALL.
When we unlock the mutex(in _mtx_unlock_sleep),we can directly
give the lock to the first thread
Daniel Eischen wrote:
On Tue, 3 Jan 2006, Scott Long wrote:
for a bit if the current lock owner is running on another CPU?
Do we currently do that?
(*) No, I am not referring to spin mutexes.
Adaptive mutexes are enabled by default and have been for at least a
year.
Ahh, then that's
Xin LI wrote:
Hi, Scott,
On 12/16/05, Scott Long [EMAIL PROTECTED] wrote:
Guys,
With code freeze for 6.1 about 6 weeks away, I'd like to put out my
'wish list' for it:
More-or-less OT question: Shall we switch ULE as the default scheduler
on -HEAD to encourage more testing against
Guys,
With code freeze for 6.1 about 6 weeks away, I'd like to put out my
'wish list' for it:
1. working kbdmux. We need this for the growing number of systems that
assume that USB is the primary keyboard. Current status appears to be
that the kbdmux driver breaks very easily. We need
Eric Anderson wrote:
Nate Lawson wrote:
Eric Anderson wrote:
I'm curious about whether a target mode device would use the buffer
cache or not. Here's a scenario:
Host A: has fibre channel host adapter, in target mode, large memory
pool, and another fiber channel host adapter connecting
Eric Anderson wrote:
Nate Lawson wrote:
Scott Long wrote:
Eric Anderson wrote:
Nate Lawson wrote:
Eric Anderson wrote:
I'm curious about whether a target mode device would use the
buffer cache or not. Here's a scenario:
Host A: has fibre channel host adapter, in target mode, large
Sergey N. Voronkov wrote:
Looks like it is broken for a while - _sym_calloc2: failed to allocate HCB
is always there...
And... Looks like Gerard Roudier havn't more interest in maintaining this
driver - there is the second generation of the original driver into linux
source three since 2001,
John Giacomoni wrote:
I am in need of a way to share memory between kernel space and possibly
multiple different user-space processes for an extended period of time.
This memory would need to be a single unpageable region.
I am using the vm routines as cribbed from mmap, however I'd like the
Charles Sprickman wrote:
Hello all,
I was just wondering about this... I recently bumped a soon-to-be
production box to 6.0 as it seems like upgrading now is easier than
doing it the week after the box goes into production (it's amazing how
the release engineering team knows to schedule
including
The FreeBSD Foundation, FreeBSD Systems, Hewlett-Packard, Yahoo!,
Sentex Communications, and SPARTA.
The release engineering team for 6.0-RELEASE includes:
Scott Long [EMAIL PROTECTED] Release Engineering,
I386 and AMD64 Release Building
Ken Smith
Dinesh Nair wrote:
On 11/03/05 03:12 Warner Losh said the following:
Yes. if you tsleep with signals enabled, the periodic timer will go
off, and you'll return early. This typically isn't what you want
either.
looks like i've got a lot of work to do, poring thru all the ioctls for
the
Dinesh Nair wrote:
On 10/28/05 16:40 Dinesh Nair said the following:
On 10/28/05 10:52 M. Warner Losh said the following:
libc_r will block all other threads in the application while an ioctl
executes. libpthread and libthr won't. I've had several bugs at work
which is a Good
Dinesh Nair wrote:
On 11/02/05 03:02 Julian Elischer said the following:
drops to splzero or similar,..
woken process called,
starts manipulating another buffer
collides with next interrupt.
that makes a lot of sense, i'll try with using splxxx() in the pseudo
driver, to block out the
Eric Anderson wrote:
Mark Kirkwood wrote:
Dear hackers,
I'm interested in being able to display some data about the contents
of the buffer cache , say file name and page offset (something like
IRIX's 'bufview').
Is there any utilities that do this currently? (searched around but
didn't
Søren Schmidt wrote:
On 28/10/2005, at 23:45, Mikhail Teterin wrote:
Indeed, 55C is way to high for 24/7 usage, and it might be that the
drive is choking on it and barely is able to compensate.
The reads are pretty quick... I'd like to be able to spin it down, but
ataidle is broken :-(
Dinesh Nair wrote:
On 10/27/05 04:16 Scott Long said the following:
an example would be using
(BUS_DMASYNC_POSTREAD|BUS_DMASYNC_PREWRITE) which
would be 0x03 in freebsd 4.x and 0x06 in freebsd 5.x. the gotcha is
that
0x03 in freebsd 4.x is BUS_DMASYNC_POSTWRITE. so therefore
Dinesh Nair wrote:
carrying on this discussion, what would be a good locking mechanism to
use to protect tsleep() and other sensitive areas in a driver in freebsd
4.x ?
the current code for the driver in 5.x uses mtx_lock and mtx_unlock with
some parts even being protected by
M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Scott Long [EMAIL PROTECTED] writes:
: Dinesh Nair wrote:
:
: carrying on this discussion, what would be a good locking mechanism to
: use to protect tsleep() and other sensitive areas in a driver in freebsd
: 4.x
John Baldwin wrote:
On Wednesday 26 October 2005 04:47 am, Dinesh Nair wrote:
On 10/26/05 10:39 Scott Long said the following:
Apparently the original poster sent his question to me in private, then
sent it again to the mailing list right as I was responding in private.
apologies
John Baldwin wrote:
On Wednesday 26 October 2005 02:13 am, Dinesh Nair wrote:
On 10/26/05 04:10 John Baldwin said the following:
Yes, and on some archs the sync() operations do have memory barriers in
place, but there isn't any bounce buffering with bus_dmamem_alloc()
memory.
and in
an error
that I found
Scott
Original Message
Subject: Re: use of bus_dmamap_sync
Date: Tue, 25 Oct 2005 07:59:03 -0600
From: Scott Long [EMAIL PROTECTED]
To: Dinesh Nair [EMAIL PROTECTED]
References: [EMAIL PROTECTED]
Dinesh Nair wrote:
hi scott,
i came across this message
Pete wrote:
Hello,
I have what may seem to be a silly question, but I cannot find any
other decent resources on the web. . The problem that I am having
right now is
that I have a fairly nice graphics card which, for the moment is only
supported on Windows Operating systems, and old 2.4
Sangwoo Shim wrote:
2005/10/12, Scott Long [EMAIL PROTECTED]:
Pete wrote:
Hello,
I have what may seem to be a silly question, but I cannot find any
other decent resources on the web. . The problem that I am having
right now is
that I have a fairly nice graphics card which, for the moment
Bruno Ducrot wrote:
On Fri, Sep 23, 2005 at 01:50:45PM +0200, Florent Thoumie wrote:
Le Vendredi 23 septembre 2005 à 12:16 +0200, Bachilo Dmitry a écrit :
Forwarding to FreeBSD hackers. (Because i am hacking WRT right now and only
Linux flashes work)
-- ??
rashmi ns wrote:
Hi,
Amazing, Thanks a lot it really works .
Now i have to read what D_VERSION does :-)
Thanks ,
Rashmi.N.S
You also need to remove .d_maj. /dev entries are created dynamically
now, and you application should have no knowledge of the major and
rashmi ns wrote:
Hello All,
While writing a pci-driver for hdlc controller which has two functions
1.BRIDGE
2.Network
Do we need to write two separate drivers for each class-code or how can a
single driver manage two different functionalites .Are there any examples on
pci-multifunction
Nikhil Dharashivkar wrote:
Hi Scott and Rajesh,
Thanks for replying me. Basically what happend, while testing
scsi driver on freebsd, at some point it crashes. So, there is no way
to know how much IO is performed. To know the IO state just before the
driver fails, i selected ktrace to
Nikhil Dharashivkar wrote:
Hi,
i want to hack the ktrace system call. Basically, I want to monitor
scsi disk IO through dastrategy() routine.
It seems that kern_ktrace.c implements different functions for
ktrace options like -tc / -ti ... etc (see man page). So, is it
possible to add new
Rajesh S. Ghanekar wrote:
Scott Long wrote:
Nikhil Dharashivkar wrote:
Hi,
i want to hack the ktrace system call. Basically, I want to monitor
scsi disk IO through dastrategy() routine.
It seems that kern_ktrace.c implements different functions for
ktrace options like -tc / -ti
the userland thread from
dastrategy that is responsible for the I/O is going to be tricky,
if even possible at all.
Scott
On 9/6/05, Scott Long [EMAIL PROTECTED] wrote:
Rajesh S. Ghanekar wrote:
Scott Long wrote:
Nikhil Dharashivkar wrote:
Hi,
i want to hack the ktrace system call
Ian Dowse wrote:
In message [EMAIL PROTECTED], Eygene A. Ryabinkin wri
tes:
What is filesystem has your USB drive?
The one I was extensively testing has FAT, but I've checked the UFS2 --
just a bit better -- 1.8 Mb/second. But you're right -- no wdrains at all.
FreeBSD 4.x had very low
Scott Long wrote:
Ian Dowse wrote:
In message [EMAIL PROTECTED], Eygene A.
Ryabinkin wri
tes:
What is filesystem has your USB drive?
The one I was extensively testing has FAT, but I've checked the UFS2 --
just a bit better -- 1.8 Mb/second. But you're right -- no wdrains at
all
Hans Petter Selasky wrote:
On Wednesday 31 August 2005 21:47, Scott Long wrote:
Scott Long wrote:
Ian Dowse wrote:
In message [EMAIL PROTECTED], Eygene A.
Ryabinkin wri
tes:
What is filesystem has your USB drive?
The one I was extensively testing has FAT, but I've checked the UFS2
John Baldwin wrote:
On Sunday 28 August 2005 10:32 am, alexander wrote:
The AMD64 arch is using the syscall/sysret opcodes instead of int80h to
perform a syscall (/usr/src/lib/libc/amd64/SYS.h). I just checked the
output my of dmesg and it says:
CPU: AMD Duron(tm) Processor (1311.69-MHz
Dan Nelson wrote:
In the last episode (Aug 05), Thordur I. Bjornsson said:
If I want to check a sysctl value from within the kernel (e.g. an
KLD), should I use the system calls described in sysctl(3) ?
If not, what is the propper way to do so ?
Since most sysctls are direct mappings onto
John Baldwin wrote:
On Friday 05 August 2005 10:50 am, Dan Nelson wrote:
In the last episode (Aug 05), Thordur I. Bjornsson said:
If I want to check a sysctl value from within the kernel (e.g. an
KLD), should I use the system calls described in sysctl(3) ?
If not, what is the propper way to
M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Jeremy Baggs [EMAIL PROTECTED] writes:
: I was wondering if anyone has done any recent work with, or knows how
: (non-)trival it would be adding support for mounting big-endian UFS
: filesystems, such as the one in use on os X.
Daniel Eischen wrote:
On Wed, 27 Jul 2005, Norbert Koch wrote:
The functions await() and asleep() in kern_synch.c
are marked as EXPERIMENTAL/UNTESTED.
Is this comment still valid? Does anyone have used
those functions successfully? Should I better not
use them in my device driver code for
Daniel Eischen wrote:
On Wed, 27 Jul 2005, Scott Long wrote:
Daniel Eischen wrote:
On Wed, 27 Jul 2005, Norbert Koch wrote:
The functions await() and asleep() in kern_synch.c
are marked as EXPERIMENTAL/UNTESTED.
Is this comment still valid? Does anyone have used
those functions
Felix-KM wrote:
I think that could work (only an idea, not tested):
struct Region
{
void * p;
size_t s;
};
#define IOBIG _IOWR ('b', 123, struct Region)
userland:
char data[1000];
struct Region r;
r.p = data;
r.s = sizeof data;
int error = ioctl (fd, IOBIG, r);
kernel:
int
1 - 100 of 225 matches
Mail list logo
