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.
>
I've been using :
make buildkernel -DKERNFAST
which is quite fast compared to the regular buildkernel. There may be a
faster way yet.
On Thu, Aug 14, 2014 at 3:28 PM, Russell L. Carter
wrote:
>
>
> ps: a quick question about quickly building modules: Suppose I have
> a fully populated /usr/
I measured some transfer rates, and have appended them.
On 08/11/14 13:53, John Baldwin wrote:
> On Saturday, July 19, 2014 1:28:19 pm John Baldwin wrote:
>> On Thursday 17 July 2014 19:45:56 Julian Elischer wrote:
>>> On 7/15/14, 10:34 PM, John Baldwin wrote:
On Saturday, July 12, 2014 5:14:
On Saturday, July 19, 2014 1:28:19 pm John Baldwin wrote:
> On Thursday 17 July 2014 19:45:56 Julian Elischer wrote:
> > On 7/15/14, 10:34 PM, John Baldwin wrote:
> > > On Saturday, July 12, 2014 5:14:00 pm Rick Macklem wrote:
> > >> Yonghyeon Pyun wrote:
> > >>> On Fri, Jul 11, 2014 at 09:54:23AM
On Sunday 20 July 2014 11:56:38 Garrett Wollman wrote:
> In article <201407151034.54681@freebsd.org>, j...@freebsd.org writes:
> >Hmm, I am surprised by the m_pullup() behavior that it doesn't just
> >notice that the first mbuf with a cluster has the desired data already
> >and returns without
Garrett Wollman wrote:
> In article <201407151034.54681@freebsd.org>, j...@freebsd.org
> writes:
>
> >Hmm, I am surprised by the m_pullup() behavior that it doesn't just
> >notice that the first mbuf with a cluster has the desired data
> >already
> >and returns without doing anything.
>
> The
In article <201407151034.54681@freebsd.org>, j...@freebsd.org writes:
>Hmm, I am surprised by the m_pullup() behavior that it doesn't just
>notice that the first mbuf with a cluster has the desired data already
>and returns without doing anything.
The specification of m_pullup() is that it re
On Thursday 17 July 2014 19:45:56 Julian Elischer wrote:
> On 7/15/14, 10:34 PM, John Baldwin wrote:
> > On Saturday, July 12, 2014 5:14:00 pm Rick Macklem wrote:
> >> Yonghyeon Pyun wrote:
> >>> On Fri, Jul 11, 2014 at 09:54:23AM -0400, John Baldwin wrote:
> On Thursday, July 10, 2014 6:31:43
On 7/15/14, 10:34 PM, John Baldwin wrote:
On Saturday, July 12, 2014 5:14:00 pm Rick Macklem wrote:
Yonghyeon Pyun wrote:
On Fri, Jul 11, 2014 at 09:54:23AM -0400, John Baldwin wrote:
On Thursday, July 10, 2014 6:31:43 pm Rick Macklem wrote:
John Baldwin wrote:
On Thursday, July 03, 2014 8:5
On Saturday, July 12, 2014 5:14:00 pm Rick Macklem wrote:
> Yonghyeon Pyun wrote:
> > On Fri, Jul 11, 2014 at 09:54:23AM -0400, John Baldwin wrote:
> > > On Thursday, July 10, 2014 6:31:43 pm Rick Macklem wrote:
> > > > John Baldwin wrote:
> > > > > On Thursday, July 03, 2014 8:51:01 pm Rick Mackle
On Sat, Jul 12, 2014 at 05:14:00PM -0400, Rick Macklem wrote:
> Yonghyeon Pyun wrote:
> > On Fri, Jul 11, 2014 at 09:54:23AM -0400, John Baldwin wrote:
> > > On Thursday, July 10, 2014 6:31:43 pm Rick Macklem wrote:
> > > > John Baldwin wrote:
> > > > > On Thursday, July 03, 2014 8:51:01 pm Rick Ma
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
Yonghyeon Pyun wrote:
> On Fri, Jul 11, 2014 at 09:54:23AM -0400, John Baldwin wrote:
> > On Thursday, July 10, 2014 6:31:43 pm Rick Macklem wrote:
> > > John Baldwin wrote:
> > > > On Thursday, July 03, 2014 8:51:01 pm Rick Macklem wrote:
> > > > > Russell L. Carter wrote:
> > > > > >
> > > > > >
On Fri, Jul 11, 2014 at 09:54:23AM -0400, John Baldwin wrote:
> On Thursday, July 10, 2014 6:31:43 pm Rick Macklem wrote:
> > 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
On Thursday, July 10, 2014 6:31:43 pm Rick Macklem wrote:
> 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:
> > > >
> > > > > Could you please post the dmesg stuff for
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:
> > >
> > > > Could you please post the dmesg stuff for the network
> > > > interface,
> > > > so I can tell what driver is being
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:
> >
> > > 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
Russell L. Carter wrote:
>
>
> 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 migh
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
Russell L. Carter wrote:
>
>
> 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
>
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
> hw.em.enable_msix: 1
> hw.igb.enable_msix:
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
hw.em.enable_msix: 1
hw.igb.enable_msix: 1
hw.ix.enable_msix: 1
[...]
--
Thomas Mueller
___
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
Russell L. Carter wrote:
>
>
> 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
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
On Wed, Jul 2, 2014 at 5:04 PM, Rick Macklem wrote:
> Please try disabling TSO on the FreeBSD systems and also
> try an rsize=32768 to see if either of those have any effect.
ifconfig -tso
sysctl net.inet.tcp.tso=0
Maybe do the same for lro?
ifconfig -tso -lro
sysctl net.inet.tcp.tso=0
dev..
Russell L. Carter wrote:
> 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
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
28 matches
Mail list logo
