Richard Hodges wrote:
> > > Now TX buffers are a problem - I have to take what I get and just
> > > "deal with it". If both start address and length need to be aligned,
> > > then I'm pretty much screwed - I have to copy...
> >
> > No, exactly ythe opposite: the TX buffer is _not_ a problem. Thi
Julian Elischer wrote:
>
> The proble is that teh ethernet header is 14 bytes so you must choose
> to allighn either the whole packet, or the IP header, but you cannot do
> both.
Hm, it seems to be a waste of CPU time memory bandwidth: only the
IP and TCP headers have to be aligned but the payl
On Tue, 17 Jul 2001, Terry Lambert wrote:
> Richard Hodges wrote:
> > Go ahead and beat me up if you have to :-) But why is there _any_ issue
> > with RX buffer alignment? I get some mbufs and set the data pointer to
> > any point I want, or I get a cluster, which is always on a 2k boundary.
>
Bill Paul wrote:
> Now, before any of you armchair geniuses out there start chiming in
> with your incredibly brilliant solutions for this problem which you
> just made up on the spot, forget it. This issue has been discussed
> to death and there's just no easy way around it.
>
> Terry Lambert an
Richard Hodges wrote:
>
> On Mon, 16 Jul 2001, Bill Paul wrote:
>
> > They're "okay." The NatSemi chip has one flaw, which is that RX buffers
> > must be aligned on a 64-bit boundary. None of the more expensive NICs have
> > this restriction.
>
> Go ahead and beat me up if you have to :-) But
Bill Paul writes:
> by user programs, but these don't panic the system. In the case of
> FreeBSD/alpha, we fake it up so know about the problem but the process
> keeps running. Some OSes (e.g. Solaris) clobber the process with a
> SIGBUS. Some would argue the latter behavior is better since i
[EMAIL PROTECTED] writes:
> A more important question is "are these 32-bit cards, and if so, do they have
> enough internal buffer to do sustained 1GB transfers". Generally 32-bit PCI
> is too slow for GB, as it cant do sustained 1GB transfers. Some 32-bit GB
> cards are just a total waste
On Mon, 16 Jul 2001, Terry Lambert wrote:
> Mike Silbersack wrote:
> > How do these perform compared to the more expensive gigabit cards?
>
> Read the driver.
True, I could've done that, but it would've taken effort.
> Bill's commentary in his drivers is frequently enlightening,
> and often am
> > The OS wants the _payload_ to be aligned on a 32-bit boundary. It tries
> > to do 32-bit accesses to the IP header, and the NFS code also does 32-bit
> > accesses when trying to un-XDR NFS requests.
>
> Oh... I see... I guess you could grab an mbuf and copy just the IP
> header for that, n
On Mon, 16 Jul 2001, Bill Paul wrote:
> > On Mon, 16 Jul 2001, Bill Paul wrote:
> >
> > > They're "okay." The NatSemi chip has one flaw, which is that RX buffers
> > > must be aligned on a 64-bit boundary. None of the more expensive NICs have
> > > this restriction.
> >
> > Go ahead and beat me
The proble is that teh ethernet header is 14 bytes so you must choose
to allighn either the whole packet, or the IP header, but you cannot do
both.
On Mon, 16 Jul 2001, Soren Kristensen wrote:
> Hi,
>
> [EMAIL PROTECTED] wrote:
> >
> > In a message dated 07/16/2001 1:11:09 PM Eastern Dayligh
> On Mon, 16 Jul 2001, Bill Paul wrote:
>
> > They're "okay." The NatSemi chip has one flaw, which is that RX buffers
> > must be aligned on a 64-bit boundary. None of the more expensive NICs have
> > this restriction.
>
> Go ahead and beat me up if you have to :-) But why is there _any_ issue
On Mon, 16 Jul 2001, Bill Paul wrote:
> They're "okay." The NatSemi chip has one flaw, which is that RX buffers
> must be aligned on a 64-bit boundary. None of the more expensive NICs have
> this restriction.
Go ahead and beat me up if you have to :-) But why is there _any_ issue
with RX buffer
>
> On Monday, July 16, 2001, at 12:57 PM, Bill Paul wrote:
> [...]
> > The chip has some nifty features though: hardware VLAN tag insertion
> > and removal, TCP/IP checksum offload on receive and transmit, 2048-bit
> > multicast hash filter, and 4 pattern match buffers for use with WOL.
>
> Wh
In a message dated 07/16/2001 1:54:25 PM Eastern Daylight Time,
[EMAIL PROTECTED] writes:
> > Maybe at some point he'll "get" that the boundry issue is a pci bus-
> mastering
> > spec issue and not a controller design flaw, as he seems to harp on this
> in
> > just about every driver?
>
>
Hi,
[EMAIL PROTECTED] wrote:
>
> In a message dated 07/16/2001 1:11:09 PM Eastern Daylight Time,
> [EMAIL PROTECTED] writes:
>
> > > How do these perform compared to the more expensive gigabit cards?
> >
> > Read the driver.
> >
> > In general, they require an extra copy because of the inabil
In a message dated 07/16/2001 1:11:09 PM Eastern Daylight Time,
[EMAIL PROTECTED] writes:
> > How do these perform compared to the more expensive gigabit cards?
>
> Read the driver.
>
> In general, they require an extra copy because of the inability
> of the card to DMA on a reasonable bo
Mike Silbersack wrote:
> > For those who have gigabit ethernet NICs based on the National
> > Semiconductor DP83820 and DP83821 controller chips and want to use
> > them with FreeBSD 4.2 and 4.3, there is a driver kit now available
> > at the following URL:
> ...
> > These cards are all extremely
>
> On Fri, 13 Jul 2001, Bill Paul wrote:
>
> > For those who have gigabit ethernet NICs based on the National
> > Semiconductor DP83820 and DP83821 controller chips and want to use
> > them with FreeBSD 4.2 and 4.3, there is a driver kit now available
> > at the following URL:
> ...
> > These c
On Fri, 13 Jul 2001, Bill Paul wrote:
> For those who have gigabit ethernet NICs based on the National
> Semiconductor DP83820 and DP83821 controller chips and want to use
> them with FreeBSD 4.2 and 4.3, there is a driver kit now available
> at the following URL:
...
> These cards are all extre
For those who have gigabit ethernet NICs based on the National
Semiconductor DP83820 and DP83821 controller chips and want to use
them with FreeBSD 4.2 and 4.3, there is a driver kit now available
at the following URL:
http://www.freebsd.org/~wpaul/National/dp83820_drv.tar.gz
This kit co
21 matches
Mail list logo
