Sujet : Re: Architectural implications of locate mode I/O and channels
De : lynn (at) *nospam* garlic.com (Lynn Wheeler)
Groupes : comp.archDate : 07. Jul 2024, 18:30:58
Autres entêtes
Organisation : Wheeler&Wheeler
Message-ID : <87frslxg6l.fsf@localhost>
References : 1 2 3 4 5 6 7
User-Agent : Gnus/5.13 (Gnus v5.13)
"Paul A. Clayton" <
paaronclayton@gmail.com> writes:
In theory, non-practicing patent licensors seem to make sense, similar
to ARM not making chips, but when the cost and risk to the single
patent holder is disproportionately small, patent trolling can be
profitable. (I suspect only part of the disparity comes from not
practicing; the U.S. legal system has significant weaknesses and
actual expertise is not easily communicated. My father, who worked for
AT&T, mentioned a lawyer who repeated sued AT&T who settled out of
court because such was cheaper than defending even against a claim
without basis.)
in 90s, there was semantic analysis of patents and found that something
like 30% of "computer/technology" patents were filed in other categories
using ambiguous wording ... "submarine" patents (unlikely to be found in
normal patent search) ... waiting for somebody that was making lots of
money that could be sued for patent infringement.
other trivia: around turn of century was doing some security chip work
for financial institution and was asked to work with patent boutique
legal firm, eventually had 50 draft (all assigned) patents and the legal
firm predicted that there would be over hundred before done ... some
executive looked at the filing costs and directed all the claims be
repackaged as nine patents. then the patent office came back and said
they were getting tired of these humongous patents where the filing fee
didn't even cover the cost of reading the patents ... and directed the
claims be repackaged as at least a couple dozen paents.
-- virtualization experience starting Jan1968, online at home since Mar1970
Date | Sujet | # | | Auteur |
2 Jul 24 | Architectural implications of locate mode I/O | 64 | | John Levine |
2 Jul 24 | Re: Architectural implications of locate mode I/O | 38 | | Thomas Koenig |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | MitchAlsup1 |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 17 | | MitchAlsup1 |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 6 | | Lynn Wheeler |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 2 | | Lawrence D'Oliveiro |
5 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Terje Mathisen |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 2 | | MitchAlsup1 |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Michael S |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Lynn Wheeler |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 9 | | Bill Findlay |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 8 | | Michael S |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Bill Findlay |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 6 | | Stephen Fuld |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 5 | | MitchAlsup1 |
4 Jul 24 | Re: wisdom of the ancients, was Architectural implications of locate mode I/O | 4 | | John Levine |
4 Jul 24 | Re: wisdom of the ancients, was Architectural implications of locate mode I/O | 2 | | John Savard |
4 Jul 24 | Re: wisdom of the ancients, was Architectural implications of locate mode I/O | 1 | | John Savard |
4 Jul 24 | Re: wisdom of the ancients, was Architectural implications of locate mode I/O | 1 | | MitchAlsup1 |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Stephen Fuld |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 19 | | John Levine |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 9 | | Anton Ertl |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 6 | | Michael S |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 4 | | MitchAlsup1 |
4 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 3 | | Michael S |
4 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | MitchAlsup1 |
5 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | Joe Pfeiffer |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | Michael S |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | Robert Swindells |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | John Levine |
4 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 9 | | Thomas Koenig |
4 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 8 | | MitchAlsup1 |
4 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 7 | | Thomas Koenig |
5 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 5 | | John Levine |
5 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 4 | | MitchAlsup1 |
7 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 3 | | Paul A. Clayton |
7 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | Lynn Wheeler |
7 Jul 24 | Re: patents, Architectural implications of locate mode I/O and channels | 1 | | John Levine |
5 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | MitchAlsup1 |
3 Jul 24 | Re: Architectural implications of people who don’t understand locate mode I/O | 1 | | Lawrence D'Oliveiro |
5 Jul 24 | Re: Architectural implications of locate mode I/O | 24 | | Joe Pfeiffer |
5 Jul 24 | Re: Architectural implications of locate mode I/O | 21 | | John Levine |
6 Jul 24 | Re: Architectural implications of locate mode I/O | 18 | | Lynn Wheeler |
6 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | MitchAlsup1 |
6 Jul 24 | Re: Architectural implications of locate mode I/O | 14 | | Stephen Fuld |
6 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 7 | | John Levine |
6 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 6 | | Stephen Fuld |
6 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 5 | | John Levine |
7 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 4 | | Stephen Fuld |
7 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 3 | | Thomas Koenig |
7 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 2 | | Thomas Koenig |
7 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 1 | | Stephen Fuld |
6 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Lynn Wheeler |
1 Aug 24 | Re: Architectural implications of locate mode I/O | 5 | | Lawrence D'Oliveiro |
1 Aug 24 | Re: Architectural implications of locate mode I/O | 4 | | Stephen Fuld |
1 Aug 24 | Re: Architectural implications of locate mode I/O | 2 | | John Levine |
2 Aug 24 | Re: Architectural implications of locate mode I/O | 1 | | Stephen Fuld |
11 Aug 24 | Re: Architectural implications of locate mode I/O | 1 | | Lawrence D'Oliveiro |
8 Jul 24 | Re: Architectural implications of locate mode I/O | 2 | | Lawrence D'Oliveiro |
8 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Lynn Wheeler |
6 Jul 24 | Re: Architectural implications of locate mode I/O | 2 | | MitchAlsup1 |
6 Jul 24 | Re: Old printers, Architectural implications of locate mode I/O | 1 | | John Levine |
8 Jul 24 | Re: Architectural implications of locate mode I/O | 2 | | Lawrence D'Oliveiro |
1 Aug 24 | Re: Architectural implications of locate mode I/O | 1 | | MitchAlsup1 |