搜了下 dmesg 原始信息被重写了。。。

> I wanted to see my original bootup messages again. So I typed
> dmesg, but all I got were 'arplookup' lines.
>
> I'm puzzled, where the bootup messages have gone?

Overwritten by kernel debug messages. There have been a number of
similar questions for a while, the gist is that when the dmesg buffer
gets filled up, it starts to overwrite itself. This affects the
daily periodic output and makes it look munged. I don't think any
solution has ever been offered up - I'd certainly be interested in it :P

ref: http://lists.freebsd.org/pipermail/freebsd-questions/2004-April/042612.html

@BXIA 收到，不过好奇怪的 dmesg 。。。貌似不包含启动信息。。。 有没 linux 高手大虾帮忙解答下~~

前 20 行：

00000000000,600000002f0e0000,000001c7b4402000,0000008013bb4400,
flit[01]= 0x0000000000000000,004500080b4402fc,fcfc0b4400fcfcfc,a08000011c7b4402,
flit[02]= 0x0000000000000000,38262da900000046,0b0c02460b0cb8ee,01400000d8e75400,
flit[03]= 0x0000000000000000,1514131211100000,00000006c72f0000,0000561ca61f0400,
flit[04]= 0x0000000000000000,2d2c2b2a29282726,2524232221201f1e,1d1c1b1a19181716,
flit[05]= 0x0000000000000000,ffff88189c463800,ffffffffa0223736,3534333231302f2e,
flit[06]= 0x0000000000000000,0000248bb6920000,0000000000000000,00030062810152c3,
flit[07]= 0x0000000000000000,0000000000000000,0000000000000000,0000000000000000,
flit[08]= 0x0000000000000000,0000000000000000,0000000000000000,0000000000000000,
flit[09]= 0x0000000000000000,0000000000000000,0000000000000000,0000000000000000,
flit[10]= 0x0000000000000000,0000000000000000,0000000000000000,0000000000000000,
flit[11]= 0x0000000000000000,0000000000000000,0000000000000000,0000000000000000,
flit[12]= 0x0000000000000000,0000000000000000,0000000000000000,0000000000000000,
flit[13]= 0x0000000000000000,0000000000000000,0000000000000000,0000000000000000,
flit[14]= 0x0000000000000000,0000000000000000,0000000000000000,0000000000000000,
flit[15]= 0x0000000000000000,0000000000000000,0000000000000000,0000000000000000,
nio_dev 0000:04:00.0: _intr, new FPQ packet:
[LLP] - (MISS_ROUTE)
[PKT] - op=0x1(MP_REQ), src=0xb4402, dest=0xb4400
flit[00]= 0x0000000000000000,600000002f0e0000,000001c7b4402000,0000008013bb4400,

@BXIA 所以“> boot.log ”导出到文件~ 文件大么？看了下我的 400 行也才 28k 。
可以传个网盘？或者邮件（我的 V2 用户名）@gmail 我帮忙上传也行哈~~ 好奇这么牛的机器的 dmesg 啥样~~

@BXIA

发个 dmesg > boot.log 如何？

phoronix 确实略复杂。。。要不算个 pi 吧~~ 虽然 22 楼指出跑分没啥意义

http://www.numberworld.org/y-cruncher/#Download

<10M, 不用编译，单线程和多线程范例：（相同位数重算前次结果会被覆盖需保存）

y-cruncher bench 25m -PF:none -TD:1
y-cruncher bench 1b -TD:64

{program} bench {size} [-PF:{framework}] [-TD:{tasks}]

The valid values for {size} are:
25m, 50m, 100m, 250m, 500m,
1b, 2.5b, 5b, 10b, 25b, 50b, 100b, 250b, 500b,
1t, 2.5t

Common Parameters:

These parameters are used by multiple components in y-cruncher.

Parallel Framework:

-PF:{framework}
(Examples: "-PF:none", "-PF:cppasync")

Use the specified parallel computing framework. The valid values are:
-PF:none Disable multi-threading and sequentialize all tasks.
-PF:spawn Spawn a thread for every task.
-PF:cppasync Use C++11 Async.
-PF:winpool Use the Windows Thread Pool. (only available on Windows)
-PF:cilk Use Cilk Plus work-stealing. (only available on Windows for AVX and AVX2)


Task Decomposition:

-TD:{tasks}
(Examples: "-TD:8", "-TD:12")

Run the operation using the desired level of task decomposition.
A larger number enables more parallelism, but at the cost of more
computational and memory overhead. For most systems, setting this equal to
the number of logical cores is ideal. But forcing it higher may reduce
load-imbalance.

Note that setting this value to 1 does not disable multi-threading since
some subroutines ignore the parameter and will decompose anyway. To get a
correct single-threaded benchmark, you need to also set the parallel
framework to "none".

Disable Multi-threading: -PF:none -TD:1

AWS T2.micro 上的测试结果：
http://i.imgur.com/9lGInOK.png

下面 2 个测试能帮忙挑个跑下么~~

http://www.numberworld.org/y-cruncher/#Download
http://www.phoronix-test-suite.com/

@cxbig
@manhere

表示很常见的需求，特别很多 dz 论坛：
http://i.imgur.com/PLXkTa7.png

上面链接貌似贴反了。。 发现 FT 多次访问后要注册。。。

@loading 也许吧。。。

@xfspace 补短肯定的，不过好贵啊。。。

@Yvette 你的 link 是 14 年的，最新的如下，确切地说应该是 DELL 买了 VMWARE 80%的股票：

http://www.ft.com/fastft/405961/what-know-about-dell-emc-pact

EMC "owns an 80 per cent stake in VMware that is worth some $27bn"

http://www.ft.com/cms/s/0/142f5190-6ddb-11e5-8171-ba1968cf791a.html#ixzz3oMubnmrh

"The buyers will pay $24.05 a share in cash, and 0.111 tracking shares for each share. The tracking shares will move in-line with VMWare's stock price."

"VMWare will remain public after the transaction."

@manhere 开始有这需求因为常逛的某图片量很大的论坛限制了上传图片大小，就想找这样的软件（也可以用外链，不过也麻烦）

@jukka 普通的 jpg/png 这些

@xenme 貌似真的要研究就是存数学问题了，压缩算法，矩阵。。。无爱。。。

@lekai63 嗯，今天办个证发现某 ZF 网站也限制图片大小，只能传 80k 。。。
http://218.85.72.204:1234/fjphoto/index.jsp

@shiny 主要是我用 PHP 一般都是调用或改现成的>.<

借用一段 Q&A 回复这个问题吧，来源： http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4172.htm

Objection #1: This feature caters to having functions with many parameters - a programming style that should be discouraged.

We agree that having functions with many parameters should be discouraged. However, the reality is that many legacy APIs that programmers have to work with and will have to work with for a long time, have functions with many arguments, and making it easier to deal with such functions would solve a real problem and be materially useful.

More importantly, however, this feature has a lot of value for functions with few arguments, too. Even for functions with few arguments, when reading a call site one has relatively little information about the roles of the arguments. Having names of arguments present would make call sites more readable, regardless of the number of arguments.

补一张激光键盘照（装 b 专用^.^实际很难用>.<)
http://i.imgur.com/4CsNl1x.jpg

貌似我是第一个用货架当桌子的^.^
http://i.imgur.com/E9xqrVb.jpg

@lincanbin @zhengkai @spacewander @zhs227 @jhdxr
感谢各位指教~ 我是编程小白，没有想到原来大家都用 array 。。。因为曾经用过一份记得好像蛮出名的开源代码结果某个函数里有十几个参数，而我只需要改变其中的第十几个参数的值而已，从此对 php 有了心理阴影。。。
不过个人还是很喜欢这项特性，毕竟用 array/class 的话要知道 array key/class member 的名字又多了一层。。。

@halfcoder
c/cpp 作为效率第一的语音，牺牲便利性表示很正常
才知道 5.6 的后续版本是 7 。。。一般只用到入门级的 PHP ，上个月看 php 到 7 了吓了一跳。。。无知了>.<

@bilok 好吧，貌似你是对的，只是在能自己控制的大楼要这样。。。
http://superuser.com/questions/443178/is-it-better-to-use-a-crowded-2-4ghz-wi-fi-channel-1-6-11-or-unused-3-4-8
In big corporate networks it's common practice to use channels 1,6 & 11 because it is fairly straightforward (at least on a diagram) to design non-overlapping cells of coverage. As a home user you don't have the same constraints so it makes sense to experiment and look for the best channel.

另外发现篇很帅气的选信道文章，推荐~
http://blog.serverfault.com/2012/01/05/a-studied-approach-at-wifi-part-2/

@bilok 如果只使用 1/6/11 是正确，很难想象那么多专业评测工具给的结果会这么明显的错误。。。

比如： https://play.google.com/store/apps/details?id=cz.webprovider.wifianalyzer
http://i.imgur.com/0fJ2hGE.png

@xbb7766 如果 3 个互不干扰信道都被占满了隔壁的应该质量会更好吧？

楼主刷坏的 4530R 出不出？

剃须刀和电动牙刷请认准博朗