> FreeBSD support has been merged into the master branch of the openzfs/zfs
> repository, and the FreeBSD ports have been switched to this branch.
>
> OpenZFS brings many exciting features to FreeBSD, including:
> * native encryption
> * improved TRIM implementation
> * most recently,
Scott Long wrote on 04/17/2020 23:30:
Can you send me some link to documentation who should I create new ISO after
rebuild?
I don’t know of any docs for doing custom releases, and it looks like it’s
harder than it used to be to insert custom patches. That said, I recommend
doing the
Hi everyone!
As I see, CURRENT still uses outdated jemalloc 5.1.0 with some performance
regressions that was fixed in 5.2.1.
Are there some issues that blocking update jemalloc to recent version?
Thanks.
___
freebsd-current@freebsd.org mailing list
Scott Long wrote on 04/17/2020 18:17:
You are correct about Intel vs AMD. Comparing the full output of pciconf from
FreeBSD with the fragment of lspci from Linux suggests that there’s at least
one set of a PCIe switch and child devices that is not being enumerated by
FreeBSD. Can you send
Hi,
Again, relatively little to report on.
The review on the main patch is ongoing. It will likely be committed
next week.
I launched a call for testing, and a number of people have done so. Only
one major issue was reported, on the stable/12 version of the patch.
That’s since been
On Sat, Apr 18, 2020 at 05:01:08PM +0200, Gordon Bergling wrote:
>
> On Sat, Apr 18, 2020 at 07:20:03AM -0700, Steve Kargl wrote:
>> On Sat, Apr 18, 2020 at 03:05:25PM +0300, nonamel...@ukr.net wrote:
>>> Hi everyone!
>>>
>>> As I see, CURRENT still uses outdated jemalloc 5.1.0 with some
>>>
Hi,
Building CURRENT on my laptop takes very very long because every little
change in llvm/clang makes it recompile a complete compiler. So I want to
build with CROSS_TOOLCHAIN=xtoolchain-llvm10 (10.0) and
WITHOUT_TOOLCHAIN=yes.
In ports/pkgs the most recent versions I see are
I am not sure, that this info is correct. As far as I remember the update for
jemalloc was reverted due to build problems, on some architecture. An updated
revision has still to be commited to -CURRENT.
Gordon
On Sat, Apr 18, 2020 at 07:20:03AM -0700, Steve Kargl wrote:
> On Sat, Apr 18, 2020
On Sat, Apr 18, 2020 at 03:05:25PM +0300, nonamel...@ukr.net wrote:
> Hi everyone!
>
> As I see, CURRENT still uses outdated jemalloc 5.1.0 with some performance
> regressions that was fixed in 5.2.1.
>
> Are there some issues that blocking update jemalloc to recent version?
>
Gordon Bergling wrote:
I am not sure, that this info is correct. As far as I remember the update for
jemalloc was reverted due to build problems, on some architecture. An updated
revision has still to be commited to -CURRENT.
That's exactly what the commit log says, yes?
On Sat, Apr 18,
On 2020-04-17 17:40, Mel Pilgrim wrote:
> On 2020-04-17 13:31, Kyle Evans wrote:
>> On Fri, Apr 17, 2020 at 3:14 PM Mel Pilgrim
>> wrote:
>>>
>>> On 2020-04-17 11:35, Ryan Moeller wrote:
The FreeBSD platform support in OpenZFS does not yet include all
features present in FreeBSD’s ZFS.
Which architectures are still often built with an external toolchain?
I'd like to re-commit jemalloc 5.2.1. It was reverted because
"compilation fails for non-llvm-based platforms." I just built
tinderbox worlds with 5.2.1 with no problems, albeit with llvm.
Eric
On 2020-04-18 02:27, Rodney W. Grimes wrote:
>> FreeBSD support has been merged into the master branch of the openzfs/zfs
>> repository, and the FreeBSD ports have been switched to this branch.
>>
>> OpenZFS brings many exciting features to FreeBSD, including:
>> * native encryption
>> *
13 matches
Mail list logo
