- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 7 2018
May 29 2018
May 24 2018
Update patch wrt newer head.
May 14 2018
It is on my queue. The plan is to use so_error for this mark, instead of SS_ISDISCONNECTING.
Hey guys, I know that ifdefs suck, but still going to forward with checking this in. If you can suggest some change to ifdefs, I am open to that. E.g. keep them minimal, so there is no duplication between debug and !debug case. Or you may prefer to keep the maximal, so that code is more readable. I can do either, but I'd like to get forward with this change.
May 1 2018
Apr 27 2018
In D15199#320705, @markj wrote:I think all of these inline ifdefs make the code a lot harder to read. Could we instead introduce wrapper functions for the ctor and dtor and hide the logic there?
Apr 26 2018
Apr 25 2018
Apr 19 2018
I did not do this in the past because it was not possible to add or increment 64-bit counters atomically. Did this change? Instead of providing bad values I decided to follow the words of the RFC.
Apr 16 2018
Apr 12 2018
In D14980#316840, @mav wrote:Is this API and device classification exist somewhere else, or being just designed? Differentiation between STRIPE, MIRROR and RAID sound somewhat odd to me, same as between SPINNING and CDROM. Besides it duplicates "GEOM::rotation_rate" attribute, we already have and use in some places (though obviously it is not passed through UFS).
Apr 11 2018
- Support vnode backed md(4).
- Bump disk version.
Apr 10 2018
Instead of using strcmp() augment struct disk with media info.
Apr 5 2018
# df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/mirror/prim 3095920 1129672 1718576 40% / /dev/md5 5061628 24 5061604 0% /var/svm /dev/nda1p8 3585929296 3084809040 214245920 94% /usr/local/www/2 /dev/mirror/logs 51581936 8159504 39295880 17% /var/log /dev/ada0p8 897802144 745401144 80576832 90% /usr/local/www/a /dev/da16p1 7691453560 6677369072 398768208 94% /usr/local/www/12 # ./pathconf-media /usr/local/www/12 /usr/local/www/12=2001<SPINNING,SCSI> # ./pathconf-media /usr/local/www/a /usr/local/www/a=1002<SOLID,ATA> # ./pathconf-media /var/log/ /var/log/=11002<SOLID,ATA,MIRROR> # ./pathconf-media /usr/local/www/2 /usr/local/www/2=2<SOLID> # ./pathconf-media /var/svm/ /var/svm/=8<MEMORY> # ./pathconf-media / /=10002<SOLID,MIRROR>
Apr 4 2018
Apr 3 2018
Apr 2 2018
Mar 22 2018
Mar 21 2018
Mar 20 2018
Mar 14 2018
My version doesn't allocate tcptw for local case, creating one on stack.
Mar 13 2018
Feb 9 2018
Feb 7 2018
Feb 6 2018
Jan 31 2018
A bigger approach to boot_pages management. The most important
change is that we actually can ask VM for pages much earlier
than we do now right after vm_page_startup(), thus do so.
Jan 26 2018
Jan 25 2018
Jan 5 2018
Dec 7 2017
Dec 6 2017
Dec 5 2017
Nov 28 2017
Nov 22 2017
Nov 21 2017
My fault, thanks for fixing.
Nov 13 2017
Nov 8 2017
Oct 19 2017
D12405 looks good to me. Matches set of changed I had with 4.9.0. Is reduced actually, since tcpdump has incorporated some of our changes since.
Hi! I think phabrickator is useless for such kinds of things. Did you follow instructions in vendor/tcpdump/FreeBSD-upgrade?
Oct 12 2017
Oct 11 2017
Oct 10 2017
SUS specifies ECONNRESET for write(2), but BSD systems never did that. SUS also specifies EPIPE, and doesn't provide any clue when ECONNRESET is preferred over EPIPE. They got very similar descriptions.
I'm sorry for accepting the previous patch too fast, without investing time into proper review.
My suggestion is to commit in two patches. First, revert r324405. Second, move of SS_ISCONNECTED check.
Oct 9 2017
The change doesn't affect sfbufs at all.
Oct 7 2017
Yes, it will be. It is split in commits in my git repo.
Oct 6 2017
Can you please grab the PR? :)
Oct 2 2017
How is that possible that tcp_usr_send leads to tcp_connect and in_pcbbind? Shouldn't we get immediate ENOTCONN if we try to sendfile on a not connected socket?
That's an interesting finding! However, I don't like that we are blindly following write() or send() logic. Copy-pasting the ERESTART is definitely superfluous. I'm pretty sure that protocols shall never return that. More complex question is that why are we sure that EAGAIN confirms that all bytes sent were actually sent? Could be bug not in sendfile, but in write :) Let me dig more on that.
Does this fix this bug? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217401
Sep 26 2017
Sep 16 2017
Sep 14 2017
It is possible to separate white space changes from the rest of changes? Do you have this in git or are you using just modified subversion workdir?