On 01/12/17 16:08, Rick Macklem wrote:
Slawa Olhovchenkov wrote:
On Thu, Jan 12, 2017 at 01:13:58PM +0700, Eugene Grosbein wrote:
12.01.2017 6:50, Slawa Olhovchenkov пишет:
On Wed, Jan 11, 2017 at 03:20:22PM -0800, Michael Sinatra wrote:
On 01/11/17 14:59, Slawa Olhovchenkov wrote:
On Wed
On 01/24/16 23:25, Ian Smith wrote:
On Sun, 24 Jan 2016 17:41:17 -0700, Russell L. Carter wrote:
> Hi,
>
> I am making myself learn better how ipfw works. I am curious about
> the optimal location of the NAT rule definition code. My immediate
> application is a
Hi,
I am making myself learn better how ipfw works. I am curious about
the optimal location of the NAT rule definition code. My immediate
application is a generic NATing gateway with an outside iface armored
up and an inside iface permitting general anarchy. The usual services
will be accessib
On 12/18/14 08:37, Adam Vande More wrote:
On Thu, Dec 18, 2014 at 9:29 AM, Alan Somers wrote:
On Wed, Dec 17, 2014 at 6:54 PM, Russell L. Carter
wrote:
On 12/17/14 18:30, Adam McDougall wrote:
On 12/17/2014 19:47, Russell L. Carter wrote:
On 12/17/14 16:07, Rick Macklem wrote
On 12/17/14 18:30, Adam McDougall wrote:
On 12/17/2014 19:47, Russell L. Carter wrote:
On 12/17/14 16:07, Rick Macklem wrote:
If this is using an exported ZFS volume, it would be nice if you
could do the same test using an exported UFS file system, to see if
this is ZFS related.
It is
On 12/17/14 16:07, Rick Macklem wrote:
Russell L. Carter wrote:
[...]
After figuring out a way to test this reversibly, I tried the
following:
server & client vfs.timestamp_precision=3, make -j12
buildworld/kernel,
and make installworld -j1 on the client => fail, in /usr/src/s
On 12/16/14 20:39, Russell L. Carter wrote:
On 12/16/14 11:37, John Baldwin wrote:
On Monday, December 15, 2014 3:59:29 pm Rick Macklem wrote:
[...]
What I suspect might cause this is one of two things:
1 - The modify time of the file is now changing at a time the Linux
client
On 12/16/14 11:37, John Baldwin wrote:
On Monday, December 15, 2014 3:59:29 pm Rick Macklem wrote:
[...]
What I suspect might cause this is one of two things:
1 - The modify time of the file is now changing at a time the Linux
client doesn't expect, due to changes in ZFS or maybe TOD c
On 08/14/14 11:35, Christopher Forgeron wrote:
> I've been using :
>
> make buildkernel -DKERNFAST
6s for the up-to-date run through, 12s to install.
Much better!
Thanks,
Russell
>
> which is quite fast compared to the regular buildkernel. There may be a
> faster way yet.
>
;>>>>> John Baldwin wrote:
>>>>>>>>> On Thursday, July 03, 2014 8:51:01 pm Rick Macklem wrote:
>>>>>>>>>> Russell L. Carter wrote:
>>>>>>>>>>> On 07/02/14 19:09, Rick Macklem wrote:
>>>>>>&g
On 07/29/14 13:48, Rick Macklem wrote:
> Russell L. Carter:
>
> The "directories within a file system" exports are only enforced by
> the Mount protocol that NFSv3 uses to talk to mountd. (NFSv4 does not
> use the Mount protocol.) These are considered "administ
On 07/29/14 11:21, John-Mark Gurney wrote:
> Rick Macklem wrote this message on Mon, Jul 28, 2014 at 18:47 -0400:
>> Russell L. Carter wrote:
>>> On 07/28/14 05:55, Rick Macklem wrote:
>>>
>>>> Assuming /export is one file system on the server, put
On 07/28/14 05:55, Rick Macklem wrote:
> Assuming /export is one file system on the server, put all
> the exports in a single entry, something like:
> V4: /export -sec=sys -network 10.0.10 -mask 255.255.255.0
> /export/usr/src /export/usr/obj /export/usr/ports /export/packages
> /export/librar
Hi,
Still a newbie here after more than ae decade off. This is most
likely a stupid question but I have invested an inordinate amount of
effort to figure it out with no success. That is, I have not resorted
to digging down into the source code to understand the error message.
I will do so if I a
On 07/12/14 14:14, Rick Macklem wrote:
> Russell seemed to confirm that the patch fixed the problem for him,
> but since I don't have em(4) hardware, it would be nice to have someone
> with commit privilege and access to em(4) hardware test and commit it.
With Rick's quite minimal patch, NFSv4
On 07/03/14 17:51, Rick Macklem wrote:
> Well, I took a quick look at the driver and it does use m_defrag(), but
> I think that the "retry:" label it does a goto after doing so might be in
> the wrong place.
>
> The attached untested patch might fix this.
>
> Is it convenient to build a kernel
On 07/03/14 00:07, Thomas Mueller wrote:
> On Wed, 02 Jul 2014 17:38:29 -0700, Russell L. Carter wrote:
>> On the second suggestion:
>>
>> root@feyerabend> sysctl -a | grep dev.em | grep enable_
>> root@feyerabend>
>
> tmu:~$ sysctl -a | grep msix
>
On 07/02/14 19:09, Rick Macklem wrote:
> Could you please post the dmesg stuff for the network interface,
> so I can tell what driver is being used? I'll take a look at it,
> in case it needs to be changed to use m_defrag().
em0: port 0xd020-0xd03f mem
0xfe4a-0xfe4b,0xfe48-0xfe49ff
On 07/02/14 17:17, Michael Sierchio wrote:
> sysctl net.inet.tcp.tso=0
Woot! 2.7MB/s -> 76MB/s
Is this a FAQ somewhere? I spent a long time looking
today and didn't find it (I do recall seeing a mention
of TSO but not seeing how to do it or that it fixed
the problem)
On the second suggestion
Greetings!
It's been 14 years. OMG do I love poudriere and zfs.
But apropos of this post from last January:
http://lists.freebsd.org/pipermail/freebsd-net/2014-January/037547.html
I am going to capitalize READ to emphasize that all I am looking at
here is reading on the client. In some of post
Greetings,
It is not easy to get kame up and running, and I know this because
I have. It is beyond all ordinary production installations.
And as Craig notes it's not possible[1] in the 5* line
yet. Maybe Randall would like to chip in on whether BSD SCTP
is ready for prime time in FreeBSD. But
21 matches
Mail list logo
