Adding Flow Director sysctls to ixgbe(4) (was: netmap: traffic distribution)

2013-09-27 Thread hiren panchasara
On Thu, Sep 26, 2013 at 10:38 AM, hiren panchasara < hiren.panchas...@gmail.com> wrote: > > > > On Thu, Sep 26, 2013 at 12:58 AM, Michio Honda wrote: > >> Hi, >> >> The handiest way to try flexible flow distribution is using Flow Director. >> I've confirmed that the patch posted to this list two y

Re: Adding Flow Director sysctls to ixgbe(4) (was: netmap: traffic distribution)

2013-09-27 Thread Adrian Chadd
On 27 September 2013 00:43, hiren panchasara wrote: > Takuya, > > I see a lot of responses/comments on proposed changes. Was anything decided > at the end of it? As far as I can tell, its still not committed to the > tree. > I'd rather see an ioctl API for that chipset and then have a separate t

Re: kern/172113: [panic] [e1000] [patch] 9.1-RC1/amd64 panices in igb(4): m_getjcl: invalid cluster type

2013-09-27 Thread Eugene Grosbein
The following reply was made to PR kern/172113; it has been noted by GNATS. From: Eugene Grosbein To: bug-follo...@freebsd.org Cc: Jack Vogel , George Neville-Neil , John Baldwin Subject: Re: kern/172113: [panic] [e1000] [patch] 9.1-RC1/amd64 panices in igb(4): m_getjcl: invalid cluster

Re: Adding Flow Director sysctls to ixgbe(4) (was: netmap: traffic distribution)

2013-09-27 Thread Takuya ASADA
Hi, I think there were many comment which says "don't use device specific sysctls, we should have more generic interface to configure NIC filter, like Linux's ethtool". And I heard same idea in last BSDCan, but there's still no proposal of "generic interface for NIC filter", I suppose. So, honestl

Re: Adding Flow Director sysctls to ixgbe(4) (was: netmap: traffic distribution)

2013-09-27 Thread Adrian Chadd
I don't care about whether there's a generic API right now. I'd rather see it done as a staged thing, but _not_ sysctls. Having sysctls to add/remove entries from things is just plain evil. I'd rather instead come up with a device specific ioctl API for this for now w/ a userland tool for each pa

Re: Adding Flow Director sysctls to ixgbe(4) (was: netmap: traffic distribution)

2013-09-27 Thread Takuya ASADA
2013/9/27 Adrian Chadd > On 27 September 2013 00:43, hiren panchasara > wrote: > > >> Takuya, >> >> I see a lot of responses/comments on proposed changes. Was anything >> decided >> at the end of it? As far as I can tell, its still not committed to the >> tree. >> > > I'd rather see an ioctl API

Re: kern/172113: [panic] [e1000] [patch] 9.1-RC1/amd64 panices in igb(4): m_getjcl: invalid cluster type

2013-09-27 Thread Sergey Kandaurov
I forward these mails for archives to easier track what was committed for this PR. -- Forwarded message -- From: Jack F Vogel Date: 6 August 2013 22:00 Subject: svn commit: r254002 - head/sys/dev/e1000 To: src-committ...@freebsd.org, svn-src-...@freebsd.org, svn-src-h...@freebsd.o

Re: kern/172113: [panic] [e1000] [patch] 9.1-RC1/amd64 panices in igb(4): m_getjcl: invalid cluster type

2013-09-27 Thread pluknet
Synopsis: [panic] [e1000] [patch] 9.1-RC1/amd64 panices in igb(4): m_getjcl: invalid cluster type State-Changed-From-To: open->patched State-Changed-By: pluknet State-Changed-When: Fri Sep 27 09:00:31 UTC 2013 State-Changed-Why: The fix committed to HEAD (r254002), stable/9 (r254003), releng/9.2

Re: Adding Flow Director sysctls to ixgbe(4)

2013-09-27 Thread Julian Elischer
On 9/27/13 4:53 PM, Adrian Chadd wrote: I don't care about whether there's a generic API right now. I'd rather see it done as a staged thing, but _not_ sysctls. Having sysctls to add/remove entries from things is just plain evil. I'd rather instead come up with a device specific ioctl API for t

Re: Adding Flow Director sysctls to ixgbe(4)

2013-09-27 Thread Adrian Chadd
On 27 September 2013 03:09, Julian Elischer wrote: > On 9/27/13 4:53 PM, Adrian Chadd wrote: > >> I don't care about whether there's a generic API right now. I'd rather see >> it done as a staged thing, but _not_ sysctls. >> >> Having sysctls to add/remove entries from things is just plain evil.

Re: netmap: traffic distribution

2013-09-27 Thread hiren panchasara
I think you meant "reply-all" :-) On Fri, Sep 27, 2013 at 7:53 AM, chintu hetam wrote: > As far as i know, flow director is Intel terminology it addresses both RSS > and RFS. I think FreeBSD implementation is RFS. > > Luigi, you touched upon SW de-multiplexer, i would like to know why it's > nec

Re: Adding Flow Director sysctls to ixgbe(4) (was: netmap: traffic distribution)

2013-09-27 Thread hiren panchasara
On Fri, Sep 27, 2013 at 1:58 AM, Takuya ASADA wrote: > 2013/9/27 Adrian Chadd > >> On 27 September 2013 00:43, hiren panchasara >> wrote: >> >> >>> Takuya, >>> >>> I see a lot of responses/comments on proposed changes. Was anything >>> decided >>> at the end of it? As far as I can tell, its sti

Re: netmap: traffic distribution

2013-09-27 Thread chintu hetam
As far as i know, flow director is Intel terminology it addresses both RSS and RFS. I think FreeBSD implementation is RFS. Luigi, you touched upon SW de-multiplexer, i would like to know why it's necessary. let say i have 82599 ixgbe driver (RSS enabled)configured with 5 tuple hash. My application

Re: netmap: traffic distribution

2013-09-27 Thread Luigi Rizzo
On Fri, Sep 27, 2013 at 8:16 PM, chintu hetam wrote: > As far as i know, flow director is Intel terminology it addresses both RSS > and RFS. I think FreeBSD implementation is RFS. > > Luigi, you touched upon SW de-multiplexer, i would like to know why it's > necessary. the sw demux is only necess