the NCQ command set, but the
differences are minor enough that it doesn't matter for most applications.
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
sable for an OS that
> claims to care about performance.
You keep saying this, but I'm unclear on what you mean. Can you
explain?
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
T
- Original Message -
> From: Wojciech Puchar
> To: Scott Long
> Cc: Dieter BSD ; "freebsd-hackers@freebsd.org"
> ; "gi...@freebsd.org" ;
> "sco...@freebsd.org" ; "mja...@freebsd.org"
>
> Sent: Friday, January 18, 201
s these tests are and how completely irrelevant they are in predicting
actual workload performance. But, I'm not going to stop anyone from trying, so
give the above tunable a try
and let me know how it works.
Btw, I'm not subscribed to the hackers mailing list, so please redistr
ed, it's because they are too lazy to go beyond being argumentative
on a mailing list.
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebs
from actually happening,
though that's a topic that needs to be revisited.
Scott
On Jul 25, 2012, at 1:27 PM, Andriy Gapon wrote:
>
>
> Preamble. I am trying to understand in detail how things work at GEOM <->
> "CAM
> disk" boundary. I am looking at scsi_da an
suggestions and testing the Installer!
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Do you mind helping me update the Wiki with your
suggestions? Maybe add a usability improvements section. If not I
can get it updated later this weekend.
Also I am working on getting 7-STABLE snapshots together and embedded
images suitable for compact flash cards ala DD/physdiskwrite.exe.
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
RENT. We build every 12 hours or so for
BSDInstaller testing. Instead of me having to roll an ISO after
every change I just wait a bit and test. Works well for me and
CPU/Disk space is cheap.
Scott
___
freebsd-hackers@freebsd.org mailing
not planned on it but I guess that some bending of my arm might
be in order.
I'll look into it. We just retired a builder box for pfSense that I
might be able to use.
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org
/wiki.freebsd.org/FreeBSD/BSDInstaller2009
If folks would like to help out with the remaining needed items that
would be awesome.
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe,
you use it?
I store the address in userland TLS area, then get it when I want to
check some scheduling informations.
Interesting, I was wondering earlier today if pointing to the per-thread
syspage in from the TLS area would save the TLB invalidate that you were
concerned about.
Scott
related commits. Try
updating to the following change numbers and retesting:
189088
189107
189161
If the last one does not work, try editing /sys/dev/amr/amr.c to change
#define AMR_ENABLE_CAM 1
to
#define AMR_ENABLE_CAM 0
Scott
189161 works, also for the iir
now what?
Next set to try
updating to the following change numbers and retesting:
189088
189107
189161
If the last one does not work, try editing /sys/dev/amr/amr.c to change
#define AMR_ENABLE_CAM 1
to
#define AMR_ENABLE_CAM 0
Scott
189161 works, also for the iir
now what?
Next set to try:
189219
189229
189253
following change numbers and retesting:
189088
189107
189161
If the last one does not work, try editing /sys/dev/amr/amr.c to change
#define AMR_ENABLE_CAM 1
to
#define AMR_ENABLE_CAM 0
Scott
___
freebsd-hackers@freebsd.org mailing list
http
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-proces
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
he commit activity on March 12 is jumping out at me as being
> > suspicious. However, you are now the second person who has told me
> > about AMR problems in 7.1 recently. If you have a precise svn change
> > number, it would help greatly.
> >
> > Scott (Long)
&g
about AMR problems in 7.1 recently. If you have a precise svn change
number, it would help greatly.
Scott
my bad. the last working amr/iir is from March 12.
I first detected the problem sometime later, but not later than March 23.
So it has to be changes in that time frame.
both drivers are
hat does look a lot
better, even if it is text. And text is still required for
serial consoles.
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "free
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!
ca
On Tue, Feb 3, 2009 at 2:17 PM, Aryeh M. Friedman
wrote:
> I use a local cvs repo and I have modified a port and which to submit an
> update for it how do I generate a patch file with cvs (cvs diff seems to
> give a unusable format)?
Maybe try cvs diff -uN
the kbdmux
driver works?
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
;
> Only set it for installworld.
Was this documented somewhere after the change? This bit me some time
ago and I could not find it documented anywhere. If not can someone
add it to /usr/src/UPDATING?
Scott
___
freebsd-hackers@freebsd.org mailing list
On Tue, 2008-06-24 at 08:41 -0700, John Kozubik wrote:
>
> On Fri, 20 Jun 2008, Scott T. Hildreth wrote:
>
> >
> >
> > On Fri, 2008-06-20 at 08:39 +0200, Alexander Leidinger wrote:
> > > Quoting John Kozubik <[EMAIL PROTECTED]> (from
On Fri, 2008-06-20 at 08:39 +0200, Alexander Leidinger wrote:
> Quoting John Kozubik <[EMAIL PROTECTED]> (from Thu, 19 Jun 2008
> 14:38:11 -0700 (PDT)):
>
> > First, a bounty has been posted here:
> >
> > http://blog.kozubik.com/john_kozubik/2007/12/bounty-posted-f.html
> >
>
Maybe the bou
. Thanks again.
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
lesystem driver will read those instead.
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
stem where this type of allocation is used for
small files and those files can not be read.
Oh, so directory data can also follow this convention? Blah. Feel free
to fix that too if you want =-)
Scott
___
freebsd-hackers@freebsd.org mailing
this is no longer a viable solution, I definitely support your ideas.
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Kip Macy wrote:
> I've committed to importing i386/PAE (UP) domU support for Xen by the
> end of the year.
>
> -Kip
>
>
Excellent, thanks for the update.
-Scott Oertel
___
freebsd-hackers@freebsd.org mailing list
http://li
; feeling of what's involved in running FreeBSD under Xen?
>
> Thanks.
>
> Paul Schenkeveld
Did you ever get any info on this subject? I'm very interested in the
status of this project as well.
Thanks,
Scott Oertel
___
freebsd
effect of a feature that FreeBSD abuses for
handling interrupts. Note that amr0 and ehci2 are acting similar. It's
mostly harmless, but it does waste CPU cycles. I wouldn't expect this
on a recent version of FreeBSD, though, at least not
Markus Oestreicher wrote:
Scott Oertel schrieb:
I have 8 machines running 6.2-RELEASE, they're all under pretty
heavy load. All but one is running Dual Opterons on Tyan
motherboards, the other is running 2x Dual Core Xeon, on a
Supermicro mb. I am receiving this panic on all the mac
Scott Oertel wrote:
Hello all,
I have 8 machines running 6.2-RELEASE, they're all under pretty heavy
load. All but one is running Dual Opterons on Tyan motherboards, the
other is running 2x Dual Core Xeon, on a Supermicro mb. I am receiving
this panic on all the machines, some of th
2
panic: page fault
cpuid = 3
Uptime: 2d19h50m39s
Cannot dump. No dump device defined. ### NOTE: I've defined the dump
device now.
Automatic reboot in 15 seconds - press a key on the console to abort
Thanks,
Scott Oertel
___
freebsd-hackers
On Sun, Feb 11, 2007 at 01:31:59PM -0500, Mike Meyer wrote:
> In <[EMAIL PROTECTED]>, Scott Mitchell <[EMAIL PROTECTED]> typed:
> > Good work, this script is pretty cool! One thing that might be nice to add
> > is an option to download new packages from the packages-X
ou only ever look
in packages-X.Y-release at the moment, and those never change after the
release as far as I know.
Best regards,
Scott
--
=======
Scott Mitchell | PGP Key ID | "Eagles ma
initiator) shutdown, and some of those I/O's got lost in the process?
I guess I don't understand why the OS didn't flush all outstanding I/O
buffers after terminating the program and before finishing the shutdown.
Maybe you are doing something illegal in your driver
t the transaction got committed to
stable storage. It's been long assumed in the external storage world
that you are at the mercy of the external storage cache, so the problem
that Danny is referring to is nothing new. The real question is how
to implement the equivalent mechanism that i
FS doesn't handle devices going away unexpectedly. Fixing it involves
massive changes to both UFS and the VM system. However, sending the
AC_LOST_DEVICE is probably the right thing to do.
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lis
/usr/src/sys/FREEBIE
i386
Promise has a good relationship with FreeBSD, I would expect their
controllers to work pretty well.
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscri
n FUSE website/wiki: http://www.wizy.org/wiki/ZFS_on_FUSE
I doubt that I'd be any help making the code work, but I certainly
like to see this make to FreeBSD is possible. If there are other
things that I can do to help then I'd be open to suggestions.
--
Joseph
aking
it easy to sort through mountains of data. It's not so good at actually
collecting the packets, so I run tcpdump in raw collection mode and then
feed the output to ethereal for analysis. Having tcpdump generate a
circular ring of files that are at most 20MB works be
EHOSTDOWN comes from the ARP layer of the IP stack, and would be
consistent with the host either getting no arp response or rejected
responses from the target. It would be useful to run tcpdump+ethereal
on your connection to see what is really going on.
Scott
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
asked
about userland access. Other than the silly case of people trying
to write device drivers in PERL, I'm not sure how much value it
gives compared to the stability and security risk it imposes.
Scott
___
freebsd-hackers@freebsd.org mailing list
chance this can be leveraged
to make ZFS work on FreeBSD?
--
Joseph Scott
http://joseph.randomnetworks.com
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any
not to say that more work and design can't be done in this
area, but we should probably wait a bit and see what has been done
already.
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To u
gt;data_ptr is a kernel virtaul
address.
One thing to note about your code is that Local_StartIO should be called
from
within ft_map_sg instead of ft_cam_action. That way the EINPROGRESS
status of bus_dmamap_load will be handled correctly. I can' describe this
more if you have questions.
Sco
the bus_space API. Or are you trying to
allocate memory in the kernel and then give the physical address of that
memory to your card? If so then you need to use bus_dma. Both Warner
and I are happy to help guide you with these APIs.
Scott
ways a good idea to check the most up-to-date version of
the errata page on the web anyway, so it's *not* too late to update it.
How convenient. These problems needed to be addressed in the release
notes, not some on line version.
So, you're still waiting for Scott to personal
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
Robert Watson about
that before this goes into 7-CURRENT.
But thank you very much for this. It was a pleasant surprise to see
this after I had been talking to others about exactly these problems for
a few weeks. Hopefully we can get this integrated
he 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 &
n fixed a week or so ago by a commit to HEAD,
RELENG_6, and RELENG_6_1 by Colin Percival. How old is kernel?
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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
re
opies often have _less_ downside than VM games, and bigger
caches will only continue to drive that point home."
What do you think about it?
I claim that Linus is an attention whore. How about that?
Scott
___
freebsd-hackers@freebsd.org mailing
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 be
ch a feature. Thank you also
for outlining the issues for this thread in a simple manner.
--
Joseph Scott
[EMAIL PROTECTED]
http://joseph.randomnetworks.com/
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinf
ail of the scheduler.
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
or do you mean non-ported applications?
Robert Huff
"user application code" == code not in src/sys/... That means
src/lib, src/bin, src/sbin, src/usr.bin, etc.
Scott
___
freebsd-hackers@freebsd.org mailing list
http:/
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 ma
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?
It sounds like your message is, &qu
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 alw
ver names onto
users. Network and storage drivers are especially guilty of this, but
tty devices also are annoying.
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ged into 6.1 and 5.5?
Regards
--jm
Since it's not in HEAD yet, it's pretty improbable that it'll get into
5.5 and 6.1. It would be nice to get it in for 6.2 though.
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.o
recall reading anything on the mailing lists.
The person working on it was Devon O’Dell (http://www.sitetronics.com/
wordpress/). I haven't seen any updates on his blog about it for
quite some time (September 2005 ?).
--
Joseph Scott
[EMAIL PROTECTED]
http://josep
g the operational
changes that you describe in your documentation.
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
lem that
turning off USB2 but leaving plain USB on avoids the problem. I'm not
exactly sure how or why this is, but it's worth a try I guess.
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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
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 m
s requires kernel
threads to be operational early on in the startup of the DomU kernel,
much earlier than what FreeBSD allows. My attempts so far to allow
xenbus to synchronously retrieve its devce configuration instead of
relying on asynchronous messages has been unsuccessfu
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
___
freeb
cov and spend some
quality time with it tonight.
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 m
o way for command
completions to be seen when interrupts are disabled. Beyond that, I
somewhat suspect that the USB stack expects to be able to push command
completion work off to worker threads, at least for some situations, and
that also will not work in the kernel dump environment. S
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
re
te has no effect.
Reading the lapic after the write makes it work.
Hmm, perhaps the read forces the write to post? Scott?
Either that, or the read imposes enough delay to let whatever was
happening during the DELAY call work. I find it hard to believe that
uncached writes would get delayed
is some work in process to
make them true threads within one or more processes.
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
body else has reported the same problem,
I'm content with a local workaround. It's just... wierd.
Craig
This points to a bus coherency problem. I wonder if your BIOS is
incorrectly setting the memory region of the apics as cachable. You'
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&#
efault and have been for at least a
year.
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 mo
ds). A co-worker of mine tried to install 6.0 using just the
handbook install guide, and discovered that it really doesn't match
reality anymore, in both big and small ways. Contact me directly if
you would like his list of comments.
Thanks!
Scott
_
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 m
l. However, it does mean that control has to
cross the kernel-userland boundary at least once for every event.
What I'd suggest doing is prototyping your target emulator in userland
and evaluating the performance there, and then moving it to the ke
hree since 2001, which is newer ported to FreeBSD by the author. And
FreeBSD hooks was removed from the driver code...
May be it is a time to port siop(4) from NetBSD?
No. I'm working on fixing this right now.
Scott
___
freebsd-hackers@freebsd.o
ic region. An easy way would be
to store it in a sysctl that can be read at runtime. A harder way would
be to have the kernel dummy up an elf segment in the image activator
code that the dynamic linker could read and put into a global variable
for the program to access.
Scott
tus of this, and also is there a central
repository that tracks changes like this that I can watch?
Thanks,
Charles
I have some old patches that lock twe. They aren't quite complete or
right due to an edge case with DMA handling. I'll probably dust them
off and
luding
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
K
5, you'll see exactly this behavior. If
you use libpthread or libthr, you won't.
i use gcc -pthread, so it's libc_r on 4.x. what does 'gcc -pthread' link
to on 5.x ?
lpthread, I believe.
Scott
___
freebsd-hackers@freebsd.
help since
we're locking access to data and not necessarily execution ?
lockmgr is far to heavy-weight and complex for this.
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
at is your code trying to do, and what problems are you seeing?
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
be hard to provide such information.
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
is OK, but write speed isnt, is that on the raw
disk device or though the filesystem ?
Søren Schmidt
[EMAIL PROTECTED]
For what it's worth, I'm seeing slow write speeds on some tests with
other (non-ata) controllers. Haven't had time to isolate
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 drive
er. Note
that you shouldn't be using splhigh() unless you really know what you
are doing. Other than that, there likely isn't anything that you need
to do for 'locking' in 4.x. The kernel is non-reentrant there, so you
don't need to worry about sync
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
ple.
I honestly don't ever expect to see IOMMU code for i386. The IOMMU that
is provided by the AGP bus is fairly limited in what it can do, and
trying to coordinate its use with X would be simply a nightmare. I'm
less clear on the IOMMU that exists for amd64 and whe
1 - 100 of 377 matches
Mail list logo
