From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Jesse Huang <jesse@icplus.com.tw>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
akpm@osdl.org, jgarzik@pobox.com
Subject: Re: [PATCH 1/5] remove TxStartThresh and RxEarlyThresh
Date: Sun, 15 Oct 2006 23:59:20 +0100 [thread overview]
Message-ID: <1160953160.5732.88.camel@localhost.localdomain> (raw)
In-Reply-To: <1160947597.22522.3.camel@localhost.localdomain>
Ar Llu, 2006-10-16 am 07:26 +1000, ysgrifennodd Benjamin Herrenschmidt:
> On Sat, 2006-10-14 at 15:55 -0400, Jesse Huang wrote:
> > From: Jesse Huang <jesse@icplus.com.tw>
> >
> > Change Logs:
> > For patent issue need to remove TxStartThresh and RxEarlyThresh. This patent
> > is cut-through patent. If use this function, Tx will start to transmit after
> > few data be move in to Tx FIFO. We are not allow to use those function in
> > DFE530/DFE550/DFE580/DL10050/IP100/IP100A. It will decrease a little
> > performance.
>
> Somebody patented FIFO thresholds ? Gack ?
3COM hold several patents on certain kinds of early interrupt/early
start for network FIFOs. At least historically they also had a GPL Linux
driver that didn't use that feature on their own cards which I'm told
was fear of patent "leakage"
Alan
next prev parent reply other threads:[~2006-10-15 22:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-14 19:55 [PATCH 1/5] remove TxStartThresh and RxEarlyThresh Jesse Huang
2006-10-15 21:26 ` Benjamin Herrenschmidt
2006-10-15 22:59 ` Alan Cox [this message]
2006-10-16 1:39 ` Valdis.Kletnieks
-- strict thread matches above, loose matches on Subject: below --
2006-10-02 18:23 Jesse Huang
2006-10-02 6:53 ` Andrew Morton
2006-10-02 7:00 ` Roland Dreier
2006-10-02 7:10 ` Jesse Huang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1160953160.5732.88.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=jesse@icplus.com.tw \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).