我沒能力判高下
Some OpenSSL and SSL certificate basics
I'm writing this down for the traditional reason, that being to try tofix it in my mind for the next time I have to deal with all of thisstuff (which will probably be in about a year):
- a SSL key is basically a blob of data. It has no interesting attributesassociated with it, and it is thus reusable if you want to. There areprobably OpenSSL commands to dump key information, but I haven't looked.
SSL keys are generated with
openssl genrsa. It
悶蛋
我之為我，無可奈何
第一點我絕無異議。本人天生凡事都喜 polish 一番，寫文章如是，下廚如是，打掃家居如是，連戴著的眼鏡也要經常除下來抹，以
Things that limit the performance of hardware acceleration
Suppose that you have an infinitely fast hardware accelerator, one thatcan compute something of interest in no time at all. What externalissues limit the total performance advantage that you can get by puttingthis hardware accelerator in a system?
I can think of the following limiters:
- main memory speed limits , the latency andbandwidth limits of system RAM. This limits how fast you caninteract with system memory.
- the speed limits of the underlying hardware that you're talking to,if you are. For example, hardware RAID
Merry Christmas!
Merry Christmas! May you have a blessed day with your family, or with the Holy Family in your heart!
從吃人肉說起
Linux's non-strict overcommit is the right default
I've written before about Linux's overcommit settings and the general background of virtual memorylimits . Several years of experience ofrunning various general use systems with strict overcommit and payingattention to the numbers have convinced me of something: non-strictovercommit is the right default on Linux , and probably on any modernUnix in general.
I have come to this view through experimental evidence, namely thatall of our user login machines generally run with significant amountsof committed address space, yet they have lots of free memory