Date: Sat, 11 Jun 2011 23:22:11 -0700 From: Navdeep Parhar <nparhar@gmail.com> To: "K. Macy" <kmacy@freebsd.org> Cc: freebsd-net@freebsd.org Subject: Re: FreeBSD I/OAT (QuickData now?) driver Message-ID: <20110612062211.GA31301@itx> In-Reply-To: <BANLkTi=VspGAjP2W9ttLHpw%2BcH1SESyVFQ@mail.gmail.com> References: <BANLkTinuOS_yZYrqZ4cmU4cim%2BKFHNA=hQ@mail.gmail.com> <alpine.BSF.2.00.1106111645010.44950@fledge.watson.org> <20110611181352.GA67777@onelab2.iet.unipi.it> <BANLkTi=VspGAjP2W9ttLHpw%2BcH1SESyVFQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jun 11, 2011 at 08:07:18PM +0200, K. Macy wrote: > > I'd really encourage people to look at the code (e.g. the pkt-gen.c > > program, which is part of the archive) so you can see how easy it > > is to use. > > Provided one has a dedicated interface. Not necessarily. The T4 ASIC has more than 1K rx queues and ~64K tx queues, which can be created (and destroyed) on the fly and combined under a "virtual interface." You could have scores of such virtual interfaces, each of which would represent an ifnet to the kernel. If there's interest, cxgbe(4) can grow support for virtual interfaces and netmap tx/rx queues that come and go as required. Untrusted rx queues are allowed too - privileged code associates memory regions with an rx queue, untrusted code is allowed direct access to the hardware ring but can only specify offsets within the allowed memory region. Regards, Navdeep
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110612062211.GA31301>