Re: OS throws away large packets

2008-05-06 Thread Mr Y
> > > >>> Hi all, > > >>> > > >>> I'm trying to implement Large Recieve Offload for an > > >>> > > >> Ethernet driver > > >> > > >>> on FreeBSD 6.3, but all my >MTU packets are being thrown > > by the OS. > > >>> I'm using mbuf chains in this imlpementation, each mbuf is > > >>> > > >> a cluster >

OS throws away large packets

2008-04-28 Thread Mr Y
Hi all, I'm trying to implement Large Recieve Offload for an Ethernet driver on FreeBSD 6.3, but all my >MTU packets are being thrown by the OS. I'm using mbuf chains in this imlpementation, each mbuf is a cluster of MCLBYTES bytes. They are linked by the m_next pointer. The first packet being thr

MSI-X on FreeBSD 6.3

2008-04-17 Thread Mr Y
i'm having problems enabling MSI-X for my Ethernet driver on 6.3. my problem is that pci_msix_count(dev) returns 0, as if my device does not support MSI-X. where should I publish my device's MSI-X capabilities? Yony ___ freebsd-questions@freebsd.org ma

mbuf chains / records in networking

2008-04-15 Thread Mr Y
I'm porting an Ethernet driver LRO mechanism (Large Recieve Offload) from Linux to FreeBSD. I learned a bit about mbuf chains and records, but i couldn't understand whether the OS is capable of "eating" a whole mbuf record (mbuf linked using m_cat, by their m_nextpkt pointer) on the RX side. Can

tcp tuning and oprofile

2008-04-13 Thread Mr Y
Hello, I'm trying to improve my 10GigE driver performance on FreeBSD 6.3. till now I found the following tcp parameters and set them: # sysctl net.inet.tcp.sack.enable=0 # sysctl kern.ipc.maxsockbuf=16777216 is there anything else I should think about regarding tcp parameters? 2nd question: I'm

working with kdb/ddb

2008-04-09 Thread Mr Y
Hi, i'm trying to extract some memory values of my variables, but the debugger doesn't know any of my variables, saying "unknown symbol" or something like that. i get the function names in the 'trace' though, so the symbols are there. does anybody know how to read the variables after the crash?

Re: Does FreeBSD 6.3 network support TSO/LSO?

2008-04-07 Thread Mr Y
Sorry about that man. On Mon, Apr 7, 2008 at 5:32 PM, Jerry McAllister <[EMAIL PROTECTED]> wrote: > On Sun, Apr 06, 2008 at 05:54:37PM +0300, Mr Y wrote: > > > Where is your message? > > It is impolite to just stick something in a subject line and > fail to put the inf

Re: kldload: unexpected relocation type 10

2008-04-06 Thread Mr Y
> > >> > I really don't know how to get rid of this message.. > >> > > >> > I get millions of these during kldload of a driver: > >> > > >> > kldload: unexpected relocation type 10 > >> > > >> > can't see anything wrong with my Makefile, like the google threads > say, > >> so > >> > PLEASE HELP.

Does FreeBSD 6.3 network support TSO/LSO?

2008-04-06 Thread Mr Y
Thanks, Yony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: kldload: unexpected relocation type 10

2008-04-02 Thread Mr Y
> > > I really don't know how to get rid of this message.. > > > > I get millions of these during kldload of a driver: > > > > kldload: unexpected relocation type 10 > > > > can't see anything wrong with my Makefile, like the google threads say, > so > > PLEASE HELP. > > The kernel module was buil

kldload: unexpected relocation type 10

2008-04-01 Thread Mr Y
Hi, I really don't know how to get rid of this message.. I get millions of these during kldload of a driver: kldload: unexpected relocation type 10 can't see anything wrong with my Makefile, like the google threads say, so PLEASE HELP. Yony ___ freeb

Re: bus_dmamem_alloc

2008-03-23 Thread Mr Y
Hi Mark, Actualy I'm not getting any error from bus_dmamem_alloc, that's the strange thing. Yet printing the dma_map pointer shows 0 unless I use bus_dmamap_create after bus_dmamem_alloc. bus_mamap_load doesn't fail in both cases. I'm working on an Ethernet driver for FreeBSD, pinging messages lar

bus_dmamem_alloc

2008-03-20 Thread Mr Y
I'm trying to use bus_dmamem_alloc. The function man says: /* * Allocate a piece of memory that can be efficiently mapped into * bus device space based on the constraints listed in the dma tag. * A dmamap to for use with dmamap_load is also allocated. */ so I'm running: e