Re: Architectural implications of locate mode I/O and channels

Liste des GroupesRevenir à c arch 
Sujet : Re: Architectural implications of locate mode I/O and channels
De : lynn (at) *nospam* garlic.com (Lynn Wheeler)
Groupes : comp.arch
Date : 07. Jul 2024, 19: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/O64John Levine
2 Jul 24 +* Re: Architectural implications of locate mode I/O38Thomas Koenig
3 Jul 24 i+- Re: Architectural implications of locate mode I/O1MitchAlsup1
3 Jul 24 i+* Re: Architectural implications of locate mode I/O17MitchAlsup1
3 Jul 24 ii+* Re: Architectural implications of locate mode I/O6Lynn Wheeler
3 Jul 24 iii+* Re: Architectural implications of locate mode I/O2Lawrence D'Oliveiro
5 Jul 24 iiii`- Re: Architectural implications of locate mode I/O1Terje Mathisen
3 Jul 24 iii+* Re: Architectural implications of locate mode I/O2MitchAlsup1
3 Jul 24 iiii`- Re: Architectural implications of locate mode I/O1Michael S
3 Jul 24 iii`- Re: Architectural implications of locate mode I/O1Lynn Wheeler
3 Jul 24 ii+* Re: Architectural implications of locate mode I/O9Bill Findlay
3 Jul 24 iii`* Re: Architectural implications of locate mode I/O8Michael S
3 Jul 24 iii +- Re: Architectural implications of locate mode I/O1Bill Findlay
3 Jul 24 iii `* Re: Architectural implications of locate mode I/O6Stephen Fuld
3 Jul 24 iii  `* Re: Architectural implications of locate mode I/O5MitchAlsup1
4 Jul 24 iii   `* Re: wisdom of the ancients, was Architectural implications of locate mode I/O4John Levine
4 Jul 24 iii    +* Re: wisdom of the ancients, was Architectural implications of locate mode I/O2John Savard
4 Jul 24 iii    i`- Re: wisdom of the ancients, was Architectural implications of locate mode I/O1John Savard
4 Jul 24 iii    `- Re: wisdom of the ancients, was Architectural implications of locate mode I/O1MitchAlsup1
3 Jul 24 ii`- Re: Architectural implications of locate mode I/O1Stephen Fuld
3 Jul 24 i`* Re: Architectural implications of locate mode I/O and channels19John Levine
3 Jul 24 i +* Re: Architectural implications of locate mode I/O and channels9Anton Ertl
3 Jul 24 i i+* Re: Architectural implications of locate mode I/O and channels6Michael S
3 Jul 24 i ii+* Re: Architectural implications of locate mode I/O and channels4MitchAlsup1
4 Jul 24 i iii`* Re: Architectural implications of locate mode I/O and channels3Michael S
4 Jul 24 i iii +- Re: Architectural implications of locate mode I/O and channels1MitchAlsup1
5 Jul 24 i iii `- Re: Architectural implications of locate mode I/O and channels1Joe Pfeiffer
3 Jul 24 i ii`- Re: Architectural implications of locate mode I/O and channels1Michael S
3 Jul 24 i i+- Re: Architectural implications of locate mode I/O and channels1Robert Swindells
3 Jul 24 i i`- Re: Architectural implications of locate mode I/O and channels1John Levine
4 Jul 24 i `* Re: Architectural implications of locate mode I/O and channels9Thomas Koenig
4 Jul 24 i  `* Re: Architectural implications of locate mode I/O and channels8MitchAlsup1
4 Jul 24 i   `* Re: Architectural implications of locate mode I/O and channels7Thomas Koenig
5 Jul 24 i    +* Re: Architectural implications of locate mode I/O and channels5John Levine
5 Jul 24 i    i`* Re: Architectural implications of locate mode I/O and channels4MitchAlsup1
7 Jul 24 i    i `* Re: Architectural implications of locate mode I/O and channels3Paul A. Clayton
7 Jul 24 i    i  +- Re: Architectural implications of locate mode I/O and channels1Lynn Wheeler
7 Jul 24 i    i  `- Re: patents, Architectural implications of locate mode I/O and channels1John Levine
5 Jul 24 i    `- Re: Architectural implications of locate mode I/O and channels1MitchAlsup1
3 Jul 24 +- Re: Architectural implications of people who don’t understand locate mode I/O1Lawrence D'Oliveiro
5 Jul 24 `* Re: Architectural implications of locate mode I/O24Joe Pfeiffer
5 Jul 24  +* Re: Architectural implications of locate mode I/O21John Levine
6 Jul 24  i+* Re: Architectural implications of locate mode I/O18Lynn Wheeler
6 Jul 24  ii+- Re: Architectural implications of locate mode I/O1MitchAlsup1
6 Jul 24  ii+* Re: Architectural implications of locate mode I/O14Stephen Fuld
6 Jul 24  iii+* Re: ancient disks, Architectural implications of locate mode I/O7John Levine
6 Jul 24  iiii`* Re: ancient disks, Architectural implications of locate mode I/O6Stephen Fuld
6 Jul 24  iiii `* Re: ancient disks, Architectural implications of locate mode I/O5John Levine
7 Jul 24  iiii  `* Re: ancient disks, Architectural implications of locate mode I/O4Stephen Fuld
7 Jul 24  iiii   `* Re: ancient disks, Architectural implications of locate mode I/O3Thomas Koenig
7 Jul 24  iiii    `* Re: ancient disks, Architectural implications of locate mode I/O2Thomas Koenig
7 Jul 24  iiii     `- Re: ancient disks, Architectural implications of locate mode I/O1Stephen Fuld
6 Jul 24  iii+- Re: Architectural implications of locate mode I/O1Lynn Wheeler
1 Aug 24  iii`* Re: Architectural implications of locate mode I/O5Lawrence D'Oliveiro
1 Aug 24  iii `* Re: Architectural implications of locate mode I/O4Stephen Fuld
1 Aug 24  iii  +* Re: Architectural implications of locate mode I/O2John Levine
2 Aug 24  iii  i`- Re: Architectural implications of locate mode I/O1Stephen Fuld
11 Aug 24  iii  `- Re: Architectural implications of locate mode I/O1Lawrence D'Oliveiro
8 Jul 24  ii`* Re: Architectural implications of locate mode I/O2Lawrence D'Oliveiro
8 Jul 24  ii `- Re: Architectural implications of locate mode I/O1Lynn Wheeler
6 Jul 24  i`* Re: Architectural implications of locate mode I/O2MitchAlsup1
6 Jul 24  i `- Re: Old printers, Architectural implications of locate mode I/O1John Levine
8 Jul 24  `* Re: Architectural implications of locate mode I/O2Lawrence D'Oliveiro
1 Aug 24   `- Re: Architectural implications of locate mode I/O1MitchAlsup1

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal