Per-mount syncer threads and fanout for pagedaemon cleaning

[Venkatesh Srinivas]

Hi!

I've been playing with two things in DragonFly that might be of interest here.

Thing #1 :=

First, per-mountpoint syncer threads. Currently there is a single thread,
'syncer', which periodically calls fsync() on dirty vnodes from every mount,
along with calling vfs_sync() on each filesystem itself (via syncer vnodes).

My patch modifies this to create syncer threads for mounts that request it.
For these mounts, vnodes are synced from their mount-specific thread rather
than the global syncer.

The idea is that periodic fsync/sync operations from one filesystem should not
stall or delay synchronization for other ones. 


The patch was fairly simple:
http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/50e4012a4b55e1efc595db0db397b4365f08b640

There's certainly more that could be done in this direction -- the current patch
does preserve a global syncer ('syncer0') for unflagged filesystems and for
running the rushjobs logic from speedup_syncer. And the current patch preserves
the notion of syncer vnodes, which are entirely overkill when there are 
per-mount sync threads. But its a start and something very similar could apply

to FreeBSD.

Thing #2 :=

Currently when pagedaemon decides to launder a dirty page, it initiates I/O
for the launder from within its own thread context. While the I/O is generally
asynchronous, the call path to get there from pagedaemon is deep and fraught
with stall points: (for vnode_pager, possible stalls annotated)

pagedaemon scans ->
...
vm_pageout_clean -> 
 [block on vm_object locks,

 page busy]
vm_pageout_flush ->
vnode_pager_putpages ->
vnode_generic_putpages ->
_write ->   
   [block on FS locks]
b(,a,d)write -> 
 [wait on runningbufspace]

_stratgy ->

Oh my...

While any part of this path is stalled, pagedaemon is not continuing to do its
job; this could be a problem -- so long as it is not laundering pages, we are
not resolving any page shortages.

Given Thing #1, we have per-mountpoint service threads; I think it'd be worth
pushing out the deeper parts of this callpath into those threads. The idea is
that pagedaemon would select and cluster pages as it does now, but would use
the syncer threads to walk through the pager and FS layer. An added benefit
of using the syncer threads is that contention between fsync/vfs_sync on an
FS and pageout on that same FS would be excluded. The pagedaemon would not 
wait for the I/O to initiate before continuing to scan more candidates.


I've not found an ideal place to break up this callchain, but either between
vm_pageout_clean / vm_pageout_flush, or at the entry to the vnode_pager would
be good places. In experiments, I've sent the vm_pageout_flush calls off to
a convenient taskqueue, seems to work okay. But sending them to per-mount
threads would be better.

Any thoughts on either of these things? 


Hope this was interesting,
--vs;
___
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"

vm_map_findspace space search?

[Venkatesh Srinivas]

Hi,

In svn r133636, there was a commit to convert the linear search in
vm_map_findspace() to use the vm_map splay tree. Just curious, were
there any discussions about that particular change? Any measurements
other than the ones noted in the commit log? Any notes on why that
design was used rather than any other?

I've seen the 'Some mmap observations...' thread from about a year
earlier and was wondering about some of the possible designs discussed
there. In particular the Bonwick/Adams vmem allocator was brought up;
I think that something inspired by it (and strangely close to the
QuickFit malloc) would be appropriate:

Here's how I see it working:
* Add a series of power-of-two or logarithmic sized freelists to the
 vm_map structure; they would point to vm_map_entries immediately to the
 left of free space holes of a given size.
* finding free space would just pop an entry off of the free space list
 and split in the usual way; deletion could coalesce in constant time.
* Unlike the vmem allocator, we would not need to allocate external
 boundary tags; the vm_map_entries themselves would be the tags.

At least from looking at the pattern of vm_map_findspace()s on DFly,
the most common requests were for 1 page, 4 page, and 16 page-sized
holes (iirc these combined for 75% of requests there; I imagine the
pattern in FreeBSD would be very similar). The fragmentation concerns
from this would be pretty minor with that pattern...

Seem okay? Thoughts?

Thanks!
-- vs
___
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"

i386 pmap_zero_page() late sched_pin()?

[Venkatesh Srinivas]

Hi,

In the i386 pmap's pmap_zero_page(), there is a fragment...

sysmaps = &sysmaps_pcpu[PCPU_GET(cpuid)];
mtx_lock(&sysmaps->lock);
*   sched_pin();
/*map the page we mean to zero at sysmaps->CADDR2*/
pagezero(sysmaps->CADDR2);
sched_unpin();

I don't know this bit of code too well, so I don't know if the sched_pin() 
being where it is is okay or not. My first reading says its not okay; if a 
thread is moved to another CPU before it is able to pin, it will use the 
wrong sysmaps structure. Is this the case? Is it alright that the wrong 
sysmap structure is used?


Oh, Nathaniel Filardo (n...@cs.jhu.edu) first spotted this, not I.

Thanks,
-- vs
___
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"

amd64 pmap pagecopy() optimization()?

[Venkatesh Srinivas]

Hi,

In svn r127653, a microoptimized pagecopy() implementation was added to 
amd64's support.S. The pagecopy() prefetches the entire page first and 
then uses a partly-unrolled loop of loads & non-temporal stores. The 
commit notes 'it is roughly four times faster than bcopy() for uncached 
pages'.


Just wondering, how was this measured? I ported the routine to i386 and 
tried it out in userland, but found it between four and six times slower 
than the BSD and GNU libc bcopy()ies; I admit to not trying very hard to 
measure on only uncached pages though...


Also, why prefetch the entire page before the load / NT store loop? If I 
read the Intel optimization guide correctly, a loop of 
prefetch(n+1) / load / store would be a better call? (I tried this on i386 
also, it was a bit faster than the current style, but still nowhere near 
bcopy()...).


Thanks!
-- vs
___
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"

Is it possible to use the libthr.a file on a Redhat Linux?

[Srinivas Ganji]

Dear All,

I have tried to use the libthr.a library for compiling an application which
is working fine on Redhat system with libpthread library. However, I end up
with the following errors.



../lib/linux/libthr.a(thr_sem.o): In function `_sem_init':

thr_sem.c:(.text+0x100): undefined reference to `ksem_init'

thr_sem.c:(.text+0x115): undefined reference to `ksem_destroy'

../lib/linux/libthr.a(thr_sem.o): In function `_sem_destroy':

thr_sem.c:(.text+0x216): undefined reference to `ksem_destroy'

../lib/linux/libthr.a(thr_sem.o): In function `_sem_timedwait':

thr_sem.c:(.text+0x2ad): undefined reference to `ksem_timedwait'

../lib/linux/libthr.a(thr_sem.o): In function `_sem_wait':









collect2: ld returned 1 exit status

make: *** [target] Error 1



So, I have also mentioned the libc.so.7(This is also a FreeBSD libc

library) library in our application to remove the above undefined
references. So, at that time I got the following errors.



/usr/bin/ld: errno@@FBSD_1.0: TLS definition in /lib/libc.so.6 section .tbss
mismatches non-TLS definition in ../lib/linux/libc.so section .bss

/lib/libc.so.6: could not read symbols: Bad value



Here, the lib/libc.so.6 is a Redhat libc library where as
../lib/linux/libc.so is a FreeBSD library (libc.so.7).



My question is: Is it possible to use the FreeBSD libthr.a library on a
Redhat Linux distribution?



Thanks in advance.



With Regards,

Srinivas G
___
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"

Re: Usage of "files" for config

[Srinivas]

Eygene, Your reply is very helpful. Thank you very much.

On Tue, Oct 28, 2008 at 1:16 PM, Eygene Ryabinkin <[EMAIL PROTECTED]> wrote:
>> I would like to know the usage of files and files.[arch] in sys/conf.
>> Basically, I didnt get the advantage of having a common file for
>> compilation(like files) rather than an individual Makefile in each
>> subdirectory.
>
> 'files' and 'files.$ARCH' are the input directives for the config(8)
> utility.  Makefile is produced with the help of these files.  The
> rationale for having 'files' and 'files.$ARCH' is simple: there are
> platform-specific directives and common directives.

Still, I didnt get the purpose of having a common "files" file for the
kernel to generate Makefile.

I am trying to understand the advantage of this approach with the
conventional way of having a makefile for each sub-directory(device or
module) and recurse from top of kernel with a configuration file
dictating what features need to be included in the kernel.

Thanks,
Srinivas
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Usage of "files" for config

[Srinivas]

Hello,

I am a beginner of freebsd kernel. I have some doubts regarding the
Makefile generation using "files" by config. Could you plz answer the
following doubts:

I would like to know the usage of files and files.[arch] in sys/conf.
Basically, I didnt get the advantage of having a common file for
compilation(like files) rather than an individual Makefile in each
subdirectory.

I have read makefile(of mkmakefile.c in config). What is the usage of
"standard", "optional" and "mandatory" and why it is followed by
device.

What are .m files? What are they used for?

Why are some of the rules in the generated makefile *.ln like scsi_all.ln?

What is ${NORMAL_LINT} and ${NORMAL_C} in the generated makefile mean?

Thanks,
Srinivas
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [Doubt] Can a PCI device communicate with another PCI or other device?

[Srinivas]

I think a PCI device can communicate with another PCI device directly
without the intervention of the CPU.

Excerpt from "PCI Express System Architecture"
...

PCI Transaction Model - Peer-to-Peer
A Peer-to-peer transaction shown as Transaction 3 in Figure 1-5 on
page 20 is the direct transfer of data between two PCI devices. A
master that wishes to initiate a transaction, arbitrates, wins
ownership of the bus and starts a transaction. A target PCI device
that recognizes the address claims the bus cycle. For a write bus
cycle, data is moved from master to target. For a read bus cycle, data
is moved from target to master.


--S


On Wed, Oct 15, 2008 at 9:35 PM, Eduardo Morras <[EMAIL PROTECTED]> wrote:
> At 20:32 14/10/2008, you wrote:
>>
>> Hello,
>>
>> I have a small doubt.
>>
>> Suppose I have a PCI card with a general purpose CPU on it. Could it be
>> able
>> to communicate with another PCI device or ISA device(lets say IDE hard
>> disk)?
>
> You can't do it directly. You must pass through the OS driver that controls
> your card. You pass to your driver the data and it send data to other
> driver, hard disk, etc.. Note that in some OSs your driver can't pass that
> info from one driver to another and need an app that binds your driver with
> the other driver.
>
>
>> Thanks,
>> Srinivas
>> ___
>> freebsd-hackers@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
>> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
>
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

[Info required] PC Architecture

[Srinivas]

Hello,

I have a theoretical understanding of the PC architecture and the
details but have no idea of how things go under the hood(for a real
computer). I think it would be very useful for me(as well as
beginners) to know how things work real-time. Even though it is not a
correct mailing list, I am posting this because you guys are the real
hackers and know a lot about how things work inside.

I would like to know about the following. Plz add anything which you
think will be helpful for the beginners.
1. Schematic diagrams of motherboards
2. How a bios detects various kinds of buses
3. How bios and os detects the different devices present in the system
and what are their capabilities
4. How interrupts are routed inside
5. Groups where we can communicate related information

I searched a lot in the internet but I am not able to find a good
place or info that gives the detailed information.

Thanks,
Srinivas
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

[Doubt] Can a PCI device communicate with another PCI or other device?

[Srinivas]

Hello,

I have a small doubt.

Suppose I have a PCI card with a general purpose CPU on it. Could it be able
to communicate with another PCI device or ISA device(lets say IDE hard
disk)?

Thanks,
Srinivas
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

options in configuration file

[Srinivas]

Hello,

May be these are beginner questions ... could you plz answer the following
questions?

I think "options" line and "device" line are in the configuration file, in
order to support those features and devices. I see that sed script will
parse that file. Could you plz let me know what will be done in this phase
and how these lines will be transferred into gcc define directives(in the
case of options) and inclusion of source files for compilation(in case of
device).

I have seen lint in some Makefiles, but dont know why it was used. Why is
lint used?

The "device" line adds device support to the kernel. What exactly does this
mean. A more basic question is: how the devices are detected initially by
the FreeBSD with the aid of hardware and bios? I think this is a broad
topic. Could you plz provide a link if there is any info, you know, in the
net?

Thanks,

Srinivas
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

IPv6 Extension Headers

[Srinivas Goud]

Hello All,
I am working on IPv6 Extension Headers Implementation.  
I am confused with freeBSD implementation and RFC2460 specification
for Destination Options.

My interpretation from RFC2460 is that,  If a packet consists of
hop-by-hop and destination extension headers, destination header
should be inserted inside AH.
i.e., hop + AH + dst. 

But freeBSD implementation is the other way, 
i.e., hop + dst + AH.

which is correct way of implementation according to RFC2460? Please
let me know, if my interpretation is wrong.

Any help will be appreciated greatly.

Thanks,
Srinivas.


-- 
Srinivas Goud
"Everything is Nicer when shared with a Friend"
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

USB device framework in FreeBSD 4.2

[Srinivas Dharmasanam]

Nick,
I'm trying to use a modified version of the ugen driver in FreeBSD 4.2 to 
control a USB device from the kernel space and am getting a kernel crash 
with a page fault trap (trap_fatal) when I try to do open on this device.

>From a user process, I am able to open this device with no problem but when 
I call the underlying open() function from an ISR (so that I get kernel 
mode), I get this fatal trap.

The backtrace of the kernel core dump is pasted below.

Note that the usbd_transfer() function in usbdi.c has the call tsleep() that 
is causing this trap.

Can you please let me know how I would be able to access a USB device from 
the kernel space? Do I have to write another USB driver along with the 
usbdi.c interface or is there a way I can do this with the existing USB 
device framework?

Thanks,
-Srinivas


_
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

SMB driver for 4.2 SMP kernel (healthd, lmmon, etc.)

[Srinivas Dharmasanam]

Hi,
I'm not able to work the SMB driver (used by healthd, lmmon, etc.) on an 
Intel x86 FreeBSD 4.2 SMP system for getting system statistics such as the 
CPU temps, voltages, fan rpm's etc.

With a FreeBSD 4.2 single cpu kernel, all of these utilities work fine using 
the underlying SMB driver (/dev/smb0 device). However, with an SMP kernel I 
get a "device not configured" error message when doing ioctl on this device.

To reproduce the problem compile and run the findSMB.c code by itself in the 
healthd package.

Does anyone know how to fix this problem with using SMB driver on an SMP 
kernel?

Thanks,
-Srinivas


_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: TCP&IP cksum offload on FreeBSD 4.2

[Srinivas Dharmasanam]

Hi,
I'm using the Netgear GA620 Gig ethernet NIC with Tigon II chip.

Do you know if it is possible to increase the buffer size for standard sized 
ethernet frames from 512 buffers to say, 1024?

I assume I'd have to modify the firmware and the host driver to accomodate 
these buffers. I dont plan to use Jumbo frames at all, and I can reduce the 
buffers allocated for them if necessary.

Thanks,
-Srinivas



>From: [EMAIL PROTECTED] (Bill Paul)
>To: [EMAIL PROTECTED] (Kenneth D. Merry)
>CC: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
>Subject: Re: TCP&IP cksum offload on FreeBSD 4.2
>Date: Sat, 29 Sep 2001 17:02:58 -0700 (PDT)
>
>
> > > On the other hand, the Tigon III
> > > is capable of 960 megabits -- about the wire rate limit --
> > > with normal size packets, if you implement software interrupt
> > > coelescing (which doesn't help, unless you crank the load up
> > > to close to wire speed and/or do more of the stack processing
> > > at interrupt time).
>
>I've been able to get 906Mbps between two Dell PowerEdge 2550
>servers with built-in BCM5700/Tigon III chipsets with a stock
>FreeBSD kernel and the bge driver.
>
> > Having downloadable firmware is actually a huge advantage.  You can do
> > things with the Tigon II that just aren't possible with any other chip,
> > either because they don't have downloadable firmware, or because the 
>vendor
> > won't release firmware source.
> >
> > This is a problem with the Broadcom Tigon III boards, and to some extent
> > with the Tigon II.  Basically it looks like the firmware for the Tigon 
>II
> > is very hard to get now that 3Com has control of it, and I don't think
> > Broadcom will release the Tigon III firmware.  (Assuming it is a
> > firmware-based chip.)
>
>I still have a copy of the last release of the Tigon II firmware and
>the development environment (which is what I used to generate the
>firmware image included with FreeBSD). As for the Tigon III, there
>is a default firmware image included in the EEPROM on the card, which
>is auto-loaded when the chip powers up. It is possible for a driver
>to load a custom image into the NIC's memory which will override the
>auto-loaded one, and it's also possible to load a new image into
>the EEPROM, however this requires an additional manual on top of
>the BCM5700 driver developer's guide as well as the firmware development
>kit, which you can only get from Broadcom/3Com/whatever under NDA.
>
>These custom images are called "value-add" firmware which are used to
>provide features like TCP segmentation, which you can't do with the
>default firmware image. Note that the BCM5700/Tigon III only has
>a limited amount of on-board RAM (256KB, I think). You're supposed
>to be able to attach up to 16MB of static SRAM to the BCM5700. The
>BCM5701 doesn't support external SSRAM at all, which I find a little
>confusing.
>
>-Bill


_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: hot swap with ugen

[Srinivas Dharmasanam]

That was it. Thank you.

Regards,
-Srinivas


>From: Ian Dowse <[EMAIL PROTECTED]>
>To: Srinivas Dharmasanam <[EMAIL PROTECTED]>
>CC: [EMAIL PROTECTED], [EMAIL PROTECTED]
>Subject: Re: hot swap with ugen
>Date: Wed, 21 Nov 2001 10:44:24 +
>
>In message <[EMAIL PROTECTED]>, Srinivas Dharmasanam 
>writ
>es:
> >Hi,
> >I'm using the generic usb device drive ugen for controlling a USB device.
> >The problem is I'm having to reboot the computer each time I
> >disconnect/connect the device in order for FreeBSD to see the USB device.
>
>Are you running usbd (usbd_enable="YES" in /etc/rc.conf)?
>
>Ian


_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

hot swap with ugen

[Srinivas Dharmasanam]

Hi,
I'm using the generic usb device drive ugen for controlling a USB device. 
The problem is I'm having to reboot the computer each time I 
disconnect/connect the device in order for FreeBSD to see the USB device.

Is there something specific I need to do with ugen driver to support 
hot-swap capability of the USB devices.

The same USB device works fine with hot-swapt on a Windows machine. I would 
appreciate any additional information on this.

Thanks,
-Srinivas


_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Request for subscription

[srinivas k]

Hello respected Sir,
  i'm really interested in joining to the FreeBSD group.
please subscribe for me to the same. [EMAIL PROTECTED]
thanking u.

Srinivas.

_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: TCP&IP cksum offload on FreeBSD 4.2

[Srinivas Dharmasanam]

Hello,
I'm trying to use the TCP&IP checksum offload capability of the Netgear 
GA620 NIC from a SMP FreeBSD 4.2R system running on a typical PIII SBC.
I did enable TCP&IP cksum offload for receive operations by setting the 
if_hwassist flag in the driver /sys/pci/if_ti.c and verified that it is 
working. However I'm unable to offload TCP&IP checksum for the send 
operations.

For the send operation, I see that the kernel is still doing the TCP and IP 
checksum calculations although the driver has the hw_assist flag set.

Can you please let me know what else needs to be done to offload TCP and IP 
checksum for both rcv/send operations on the Tigon2 NIC?

Thanks,
-Srinivas


_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: inw and outw calls

[Srinivas Dharmasanam]

Hi,
I have a question regarding the inb/outb() or inw/outw() calls in FreeBSD 
4.2.

I have a dual fxp Fast Ethernet NIC that shows up as following with dmesg :

fxp1:  port 0xcc00-0xcc3f mem 
0xef90-0xef9f,0xefa
ff000-0xefaf irq 18 at device 12.0 on pci2
fxp1: Ethernet address 00:30:64:03:03:2a
fxp2:  port 0xc800-0xc83f mem 
0xef70-0xef7f,0xefa
fe000-0xefafefff irq 19 at device 13.0 on pci2
fxp2: Ethernet address 00:30:64:03:03:2b

Now, I need to write the Watchdog timer ctrl registers (offset 65 and 66) on 
this card.

For this I'm using outb(port, val) fn call. Can someone please tell me how 
to calculate the port no to pass to this outb() function.

I tried writing to all possible port nos starting from 0xc800 to 0xc83f
and 0xcc00-0xcc3f but it has no apparent effect on the system.

Please let me know how to translate this port range to the actual outb() fn 
call arguments.

Thanks a lot in advance.

Regards,
-Srinivas








_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: 4.2 SMP driver for DiskonChip

[Srinivas Dharmasanam]

Hi,
I'm trying to use the M-Systems', DiskonChip on a Dual PIII SBC running the 
SMP FreeBSD4.2 kernel.

However, I get kernel crashes when trying to write to the DiskonChip (on a 
4.2FreeBSD SMP kernel on a regular IDE disk) or sometimes even when I try to 
reboot from an existing FreeBSD 4.2-SMP system already on the DOC.

It seems lik the DOC driver is not 4.2FreeBSD-SMP compliant. Has anyone 
faced this problem already? I will contact the developer of the driver and 
also M-Sys about this but please let me know how you address this problem.

Thanks a lot.

Regards,
-Srinivas


_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: register new device driver

[Srinivas Dharmasanam]

I'm trying this on FreeBSD 4.2 Release.

-Srinivas

>From: Julian Elischer <[EMAIL PROTECTED]>
>To: Srinivas Dharmasanam <[EMAIL PROTECTED]>
>CC: [EMAIL PROTECTED]
>Subject: Re: register new device driver
>Date: Fri, 6 Jul 2001 14:38:15 -0700 (PDT)
>
>what version of FreeBSD are you doing this on?
>(it makes a difference)
>
>
>On Fri, 6 Jul 2001, Srinivas Dharmasanam wrote:
>
> > Hi,
> > I used the /usr/share/examples/make_device_driver.sh to create a device
> > driver in /sys/i386/isa and included my additions in the skeleton 
>provided.
> >
> > Now, I'm trying to call the mmap function with the "filed" argument 
>equal to
> > that corresponding to this new device.
> >
> > Can you please let me know what else needs to be done to register this
> > device in the kernel.
> >
> > Thanks,
> > -Sri
> > _
> > Get your FREE download of MSN Explorer at http://explorer.msn.com
> >
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-hackers" in the body of the message
> >
>

_
Get your FREE download of MSN Explorer at http://explorer.msn.com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: register new device driver

[Srinivas Dharmasanam]

Hi,
I used the /usr/share/examples/make_device_driver.sh to create a device 
driver in /sys/i386/isa and included my additions in the skeleton provided.

Now, I'm trying to call the mmap function with the "filed" argument equal to 
that corresponding to this new device.

Can you please let me know what else needs to be done to register this 
device in the kernel.

Thanks,
-Sri
_
Get your FREE download of MSN Explorer at http://explorer.msn.com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message