Is there really that much room for improvement by changing packet size? You're avoiding a little bit of overhead for the 40 byte packet header and you're also increasing the risk of that packet failing CRC and getting discarded which is a lot more expensive.
The real problem is the packet arrival rate on today’s high-speed interfaces.
At 1.6Tb/sec, with 1500 byte packets, that leaves very little time for a router to make a forwarding decision and route each packet before the next arrives. It’s kind of wild we have the same max MTU on interfaces that speed as we had with 10Mbit Ethernet.
So far we’ve kept up with some very clever engineering, but I do wonder if it can continue indefinitely.
There is much improvement to be gained by changing packet size from the current de-facto limit of 1500 byte MTU, but requiring 32-bits is likely unnecessary as just increasing it to the current 16-bit limit of 65535 bytes would be adequate for any reasonably designed protocol.
Given current compute, you would be hard-pressed to control plane more than ~100 million packets per second per core which is ~1 Tb/core-s at a 1500 byte MTU. Increasing this to just 65535 is a ~40x increase to ~40 Tb/core-s (~6.5 TB/core-s). Clocking at 5 Ghz and issuing 2 cache-line sized stores per clock you can still only issue ~640 GB/core-s (~4 Tb/core-s) of memory traffic from a core (assuming you do not get memory bandwidth limited earlier than that). So, at a 1500 byte MTU you need a 1:4 data to control core ratio, but at 65535 you flip that to a 10:1 core ratio. This should be reasonable for basically anything for the foreseeable future.
I mean over the standard 1500 byte packet, for sure. I'd assume that you'd probably find an optimal spot at 1 to 8Mb on super fast networks. Also networks at these speeds tend to have very low retry rates. It's the buffer sizes that start to get crazy though.
Yes, but they're arguing in the letter that the work is _also_ disclosing information that would allow their competitors to know how DisplayLink works. You can't have it both ways.
Yeah, that statement clearly is making IP claims beyond patent infringement, they just didn't elaborate. They didn't say it's patent infringement because of that.
1. Reverse engineering for interoperability gives you a defense for copyright and trade secret claims in the US. It provides zero protection from patent claims. "reverse engineering a patent" doesn't even make any sense. Patents are public, there's nothing to reverse engineer. You could "reverse engineer a specfiic implementation of a patent", but the only thing you'd be accomplishing is just avoiding infringing on the parts of the implementation that are subject to copyright or trade secret protections. You'd still be violating the patent.
2. I'm not saying their arguments are valid. It's a demand letter with multiple claims. There's many reasons it might be an invalid argument but listing more than one grievance and/or not explaining them in detail are not some of those reasons.
He used fenchol (a basil-like aroma), tea tree oil and tannins to replace coca leaf extract. Without tea tree oil, it did taste substantially different from coca-cola and more like Pepsi, and without tannins it was more like diet coke.
Coca isn't blanket-illegal. It's just very-heavily restricted in the States. (But not that restricted: My regular dentist is licensed to prescribe cocaine. At a federal level, it's less-restricted than the devil's lettuce is.)
Coca-Cola buys spent coca remains, after they've had the party powder components extracted from them. This product is not particularly restricted.
But lawyers are prone to using scary phrasing, even if that phrasing has no bite, and are free to write strongly-worded letters.
"I see that you've been publishing the privately-held, trade secret tomato processing technique I developed -- on the Internet! Now, tomato processors everywhere can see it! I'm really pissed! I demand that you stop doing this immediately! In fact, if you want a full enumeration of whar I really think about the terrible things you're doing, then I further demand that you pay me $25,000 for that effort!"
...it's got no bite, but it's a letter. It can be drafted and sent.
Trade secrets aren't an encumbrance if you discover them independently. Reverse engineering (for interop) is legal in the US. The only leg they have to stand on is patent infringement.
However reverse engineering, even for interop, doesn’t absolve you of EULA things you agreed to, which can include reverse engineering. And any such dispute can drag you into court for years and easily 10s of thousands of dollars, just to defend.
A EULA also is not zero legal weight. It is a contract for any legally enforceable term, for the most part. And one can sign away a lot of what you’d think cannot be signed away, such as the right to trial if you agree, even by EULA, to arbitration.
And in any case, if you want to fight a corp, you’ll easily burn through $50k min through hundreds of thousands to get through the hassle.
So simply trying to waive it away through unfounded belief is not a good strategy.
So, what? The patent is there to enforce that even if your competitors have full access to DisplayLink technology, they won't be allowed to implement it.
What is covered by the patent will be publicly available anyway after it expires. What is not covered, well it's not covered either due to their negligence or because it plainly is not patentable.
And a patent can be invalidated for the lack of enablement. I.e. for not disclosing sufficient information for an average skilled practitioner to re-implement it.
Where I'm at is that if these open source developers aren't selling or distributing the hardware for this drivers, then anyone that uses this driver implicitly has a license to the patents that they received with the hardware itself.
Trade secrets don't hold up because they're running off of public information either in the distributed binary drivers' behavior, or the behavior of the aforementioned hardware.
Copyright claims similarly don't hold because of the software interoperability exemptions.
All of that being said, I know I don't have the money laying around to fight those in court, and would be drained well before any of those points are adjudicated.
Is writting software "implementing," or is compiling it and releasing binaries (for free,) executing them, or just profiting from the sale, from the perspective of patent law? Isn't describing how something works first ammendment territory, even if the speech is compilable? (err, I guess this was Scotland & UK patent law, not the US, so 1st ammendment is, of course, irrelevant.)
That's not quite true. While there's no exemption for personal use, patented inventions can still be used for academic and research purposes. Even if you derive income from that.
E.g. it's a fair game to write and release a book: "How to Replicate DisplayLink" that would walk the reader through the steps in implementing it.
Yep. I was involved with drug research, and the only accepted use for unlicensed compounds was testing their efficacy in benchmarks against your compounds.
A program per se though is just a detailed description of the "invention" (i.e. a better version of the patent document itself). That's the entire software patent loophole; they take pure math and say "a system where a computer does the described math."
No, a program is literally, exactly, a blueprint. It is the abstract description. This can even be formally stated mathematically (i.e. programs are formal mathematical objects). Note that you can touch an office building. You can stand inside of one. You cannot touch a program. You cannot stand inside of one. There is no concrete "thing" that is the program. You can only run a program using a (universal) computing machine, which can perform any math.
Ok, call it whatever you want, all of these semantics and metaphors are legally irrelevant anyway. I still fail to see what this tangent has to do with this conversation.
Because a patent is a description of an invention. A computer program (like a driver) is also a description of some algorithm. This is not a metaphor. It is definitionally exactly true. Saying it's protected by a patent is like saying an engineering book is protected by a patent (in fact, you can print a program in... a book, and there are many programs contained in books). It's not only false, but would go against the entire purpose of a patent, which is to publish a description of the invention.
It does because patents don't cover descriptions of inventions. They cover inventions. Words in a book aren't the right "type" to be able to infringe on a patent, but they can be a computer program.
You yourself linked to a case limiting even the ability to claim that running a computer program on a computer can be patented. The program itself was never patentable.
The point is that software does not implement an invention. You're making a type error. No software does. It's like saying "a green tastes good." Green doesn't taste anything, and you can't have "a green." It's a color. When you write those words it's just a nonsense string. Software doesn't implement any patent just like 5 or pi don't implement any patent. It's a formal mathematical object. It also can't violate a patent because you can't patent mathematical objects, only inventions. An implementation of a patent may contain a computer that runs software.
It's like saying a circuit diagram could infringe on a patent. No, only a circuit can. Software is the diagram. A thing running software can infringe, but software isn't the right type of thing to be able to infringe. You can print books full of detailed diagrams and instructions all day long. The patent is already supposed to describe the thing! It's not secret! A description of every last detail is not protected!
This is also why you can prove things about software. You cannot prove things about inventions; only models of the inventions. You can actually prove statements about software itself because it is already part of formal mathematics.
Again, you are conflating "what can be patented" with "what can infringe"
If you make, use, produce, supply, induce someone to use anything that does a thing that is listed in a claim of a patent -- you have violated the patent.
The argument that "software is just abstract math and so there's no way it can infringe" is bologna... like sovcit-level bologna. Any actual articulable piece of written software is not some abstract mathematical concept, it is the configuration for a machine. Courts simply do not treat software in the way you are asserting, they treat it like a component in a system. And whether or not you built the full system or you are contributing to or inducing someone else's system, doesn't matter much, it is merely the difference between direct and indirect infringement.
If what you are asserting was true, it would be great for the software industry -- we wouldn't have to worry about patents anymore!
The Supreme Court of the US literally held that software is like a blueprint, or a detailed set of instructions. Because that's what it is:
> Abstract software code is an idea without physical embodiment, and as such, it does not match §271(f)’s categorization: “components” amenable to “combination.” Windows abstracted from a tangible copy no doubt is information—a detailed set of instructions—and thus might be compared to a blueprint (or anything else containing design information). A blueprint may contain precise instructions for the construction and combination of the components of a patented device, but it is not itself a combinable component.
Courts do actually understand that software is an abstract mathematical idea. And this is the only sane way to treat software. Otherwise you'd have e.g. Lean proofs as patentable subject matter. There is no line you can draw where you say "this is software, and that is a proof." Formal reasoning (e.g. through types) is all over real world, useful software.
For what it's worth I've never actually encountered anyone who's even mentioned patents at work in the last decade. It's not a day-to-day concern that I've seen.
Yeah, when it comes to determining the question of the country of origin for the particular way they were delivering the software -- which was what quote was about.
Courts did find MS liable for infringing on AT&T's patent for Windows installed on computers in the US. And this wasn't discussed at all in that court case; it was never challenged up to SCOTUS because it was plainly a violation.
Computers running Windows with some functionality are not the same thing as Windows. That's literally the point the court made. Windows, the software, is abstract math, and cannot on its own infringe on anything. They very clearly laid out that Windows itself is a set of instructions.
Hence they could ship the intangible software itself abroad and install it without infringing on US patent law. Merely creating the software did not infringe.
That case only ruled on §271(f). Plenty of routine FOSS activities could qualify for other violations under that statute. The most likely is probably inducement -- have a README that tells someone how to install the software on a computer? You just induced them to put together the infringing system.
In practical terms there is no point in entertaining the idea of software without any relation to a computer -- people are gonna' run software on a computer, that's what it's for.
To be clear, a patent is an exclusive right to the specific functional invention, and if that invention happens to cover the one and only way to talk to the device, then it'll be hard to make a driver. In many cases you'll be able to make one for yourself due to some funny-business around patent exhaustion.
However, there is no universe where they can hold a valid patent that would encumber a driver for a regular USB display device. What they then might try to do is invoke DMCA, due to the device having DRM responsibilities (HDCP).
If they get trusted HDCP treatment from media players on some platforms, they might fight tooth and nail to not be broken open in public as that might end up with them losing trust from content providers...
Or maybe they're just assholes with no real rhyme or reason, who knows.
> If they get trusted HDCP treatment from media players on some platforms, they might fight tooth and nail to not be broken open in public as that might end up with them losing trust from content providers...
Yeah, I suspect the whole patent claim is just a ruse to try and prevent people from looking into their likely insecure HDCP implementation.
I realize this is a legal case and not engineering logic, but man, they really seem to give away the game:
The letter continued to claim that Lothian would be "single-handedly eviscerating DisplayLink's competitive advantage in this crowded market by educating our competitors and other third parties as to how we implement our proprietary technology"
You can get around it by reverse engineering it as long as what's sold doesn't violate that patent.
Many companies have had to reverse engineer an existing patent to figure out what they can do instead.
> Design-arounds are considered to be one of the benefits of patent law. By providing monopoly rights to inventors in exchange for disclosing how to make and use their inventions, others are given both the information and incentive to invent competitive alternatives that design around the original patent. In the field of vaccines, for example, design-arounds are considered fairly easy. It is often possible to use the original patent as a guide for developing an alternative that does not infringe the original patent.
Mostly not patented software patents are fairly new to law and so probably not patentable. Even if patentable, the bios was things in common industry practice and so any patent would have expired years before
Yes. When you have 15 minutes to play, you just want to open the website and play, no figure out where to torrent things or which emulator works where and fiddling with the settings, etc.
No, but different people code for different reasons, and neither is more or less "wrong."
Some people (usually the ones who tend to like AI) see coding simply as getting a problem solved, and aren't as interested in how it happens.
Others see code as an artform, and a journey to appreciate in itself. For them, knowing that they are using their knowledge and experience to solve problems that not just anyone can, is part of the fun. It gives us a sense of worth and accomplishment, and that's why we like doing it.
To me it's similar to actual art/painting. Of course artists get upset at AI because they don't want their industry to leave them behind and make them feel unnecessary or less special.
But I don't fault the ones who don't think the way I do... it's just a different way of looking at it.
Author here. Setting aside the effort and cost involved in refurbishing the Mac itself, I can assure you this was not a one-prompt project. It required some planning and steering to build something friendly without scope creep. Despite (or because of) the non determinism, there is still an art and science to engineering by prompt.
Just as C and so forth were shortcuts to allow creativity without learning machine language and having to painstakingly manage a memory heap, LLM tools further allow us to manifest creativity.
Best description I heard is that LLMs are like “eyeglasses for the mind.” It levels the playing field for people like me who maybe don’t have time to learn classic Mac C, the retro68k dev environment, how the hell TCP/IP works at a low level, and all that. Maybe in the same way that professionally it’s allowing me to contribute to areas of the codebase that i couldn’t before and vice versa with my colleagues who used to rely on my area of expertise.
While I was certainly proud that I had some slightly unique or scarcer talent before, I don’t feel a need to be a gatekeeper about it in the new world (and I’m not suggesting you are), since I’m able to deliver a ton more value at a higher velocity now. That follows thru to personal projects like this, where I can finally do this kind of project and see results without losing too much of my precious free/family time.
I agree completely. Personally, I think the art of programming was lost the moment we started using human-readable languages.
Some people see coding as simply getting a problem solved, and aren't interested in how the CPU actually does it. Others appreciate the craft of painstakingly arranging machine instructions, understanding every register and every clock cycle, and knowing they're solving problems that not just anyone can.
For us, that's where the sense of worth and accomplishment comes from. Using a high-level language to have a compiler do all the interesting work rather misses the point.
But I don't fault people who use Python, C++, or even assembly. It's just a different way of looking at it.
reply