Hi. I've been recently upgraded to -CURRENT (9.0).
After
# make buildworld
# make buildkernel KERNCONF=MYKERNEL
# make install kernel KERNCONF=MYKERNEL
I have rebooted to single-user mode, as suggested in the documentation.
No more wireless connection. I've a intel 2200 bg wireless card,
running u
On 03/09/10 08:32, Bernhard Schmidt wrote:
> On Friday, September 03, 2010 01:34:54 Davide Italiano wrote:
> > Hi. I've been recently upgraded to -CURRENT (9.0).
> > After
> > # make buildworld
> > # make buildkernel KERNCONF=MYKERNEL
> > # make install ke
On Sat, Oct 2, 2010 at 2:36 PM, Paul B Mahol wrote:
> Hi,
>
> I see no point to have it in usr/bin.
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-c
On Mon, Aug 25, 2014 at 12:37 PM, John Baldwin wrote:
> On Wednesday, August 20, 2014 11:00:14 AM Davide Italiano wrote:
>> One of my personal goals for 11 is to get rid of cloning mechanism
>> entirely, and pty(4) is one of the few in-kernel drivers still relying
>> on su
On Thu, Nov 27, 2014 at 10:37 AM, Alfred Perlstein wrote:
>
> On Nov 27, 2014, at 1:52 AM, Konstantin Belousov wrote:
>
>> On Wed, Nov 26, 2014 at 04:41:27PM -0800, Davide Italiano wrote:
>>> On Mon, Aug 25, 2014 at 12:37 PM, John Baldwin wrote:
>>>> On We
Currently, the following is allowed in FreeBSD:
root@rabbit1:/home/davide/udp-clt # sysctl kern.ipc.nmbclusters=2147483647
kern.ipc.nmbclusters: 2036598 -> -2147483648
The following is an attempt of fixing.
I also think nmbcluster should actually be u_int and not it, but this
is a discussion for
Hi,
one of the first things I do when I install FreeBSD is to switch the
default PAGER from more(1) to less(1). This is particularly
convenient, e.g. while using git diff, to show something more
readable.
Just out of curiosity, is there a reason why more(1) is still the
default, and/or is this just
On Wed, Feb 18, 2015 at 5:18 PM, Adam McDougall wrote:
> The PAGER was less for about half a year and reverted. Please see:
>
> https://svnweb.freebsd.org/base?view=revision&revision=242643
> ___
> freebsd-current@freebsd.org mailing list
> http://lists
On Mon, Feb 23, 2015 at 5:17 PM, Allan Jude wrote:
> Upgraded my router today, because it was approaching the 24 uptime days
> of doom
>
> Now, it likes to die on me, a lot
>
>
The bt you posted suggest this could be stack overflow, probably due
to infinite recursion.
Also, as a wild guess, just
On Sat, Mar 28, 2015 at 3:02 PM, Manfred Antar wrote:
> I get the following panic on current svn ver r280793:
>
Revert to r280784. This should fix.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
On Fri, May 8, 2015 at 1:34 PM, Pedro Giffuni wrote:
> Hi;
>
>
>> I guess I see the following options:
>>
>>1) Just leave GNU RCS in the tree.
>>
>>2) Improve OpenRCS so it can be swapped in.
>>
>>3) Remove RCS dependencies from other parts of the tree (e.g.
>> etcupdate)
>> and
On Fri, Nov 11, 2011 at 4:14 PM, Alexander Yerenkow wrote:
> Hello all.
> Before I begin, I appreciate any help/comments/criticism. Please, don't
> hesitate to support this topic.
>
> Some time ago I've announced new project - of creating rolling images of
> FreeBSD from SVN.
> Along with plain st
Good evening folks.
During last days I've written a patch to add sandy bridge support to
hwpmc. Until now, the most recent Intel processor microarchitecture
supported was Westmere.
Testing is appreciated, in order to see if there's something that have
to be fixed.
You can find the diff here: http:/
On Sun, Nov 13, 2011 at 9:52 PM, Davide Italiano
wrote:
> Good evening folks.
> During last days I've written a patch to add sandy bridge support to
> hwpmc. Until now, the most recent Intel processor microarchitecture
> supported was Westmere.
> Testing is appreciated, in ord
On Sun, Nov 13, 2011 at 9:56 PM, Attilio Rao wrote:
> 2011/11/13 Davide Italiano :
>> On Sun, Nov 13, 2011 at 9:52 PM, Davide Italiano
>> wrote:
>>> Good evening folks.
>>> During last days I've written a patch to add sandy bridge support to
>>> hw
CPU)
>
> I will try to apply this to current to see if this is reproduced.
>
> 2011/11/14 Attilio Rao :
>> 2011/11/13 Davide Italiano :
>>> On Sun, Nov 13, 2011 at 9:52 PM, Davide Italiano
>>> wrote:
>>>> Good evening folks.
>>>> During l
Hi hackers,
I've taken a closer look to iap_event_westmere_ok_on_counter() and
comparing the code with the intel documentation it seems that some
events some events valid only on 0-1 counter are not listed. Maybe I'm
missing somethin', so please point me out. Otherwise, there's a patch
that should
On Sun, Nov 27, 2011 at 5:24 PM, Jilles Tjoelker wrote:
> On Sun, Nov 27, 2011 at 03:45:36PM +, Alexander Best wrote:
>> i've been playing with clang tot and noticed the following error:
>
>> /usr/local/bin/clang -c -O3 -pipe -fno-inline-functions -fno-strict-aliasing
>> -march=core2 -std=c99
On Tue, Sep 4, 2012 at 9:35 AM, Fabien Thomas wrote:
>
> Le 3 sept. 2012 à 23:23, Baptiste Daroussin a écrit :
>
>> On Mon, Sep 03, 2012 at 02:04:21PM +0200, Fabien Thomas wrote:
>>> Hi,
>>>
>>> Find a patch that add Intel Ivy Bridge support to hwpmc(9).
>>> The patch also support offcore RS
[trimming old mails]
>
> Hi,
>
> here are the results
>
> # pmccontrol -L
> SOFT
> CLOCK.STAT
> CLOCK.HARD
> LOCK.FAILED
> PAGE_FAULT.WRITE
> PAGE_FAULT.READ
> PAGE_FAULT.ALL
>
> # pmcstat -SOFF_CORE_RESPONSE_0,rsp=REQ_DMND_DATA_RD+RES_ANY -w1 -T
> p
On Mon, Nov 5, 2012 at 7:12 AM, Joe Holden wrote:
> Hi guys,
>
> Has some default changed between 9.1-RC2 and HEAD?
>
> On identical machines, one with 9.1-RC2 and one with HEAD from yesterday
> (GENERIC) I see the following in systat -v:
>
> 9.1:
> 65 cpu0:timer
> 10 cpu1:timer
>
> HEAD:
> 1127 c
On Nov 4, 2012 10:40 PM, "Joe Holden" wrote:
>
> Davide Italiano wrote:
>>
>> On Mon, Nov 5, 2012 at 7:12 AM, Joe Holden wrote:
>>>
>>> Hi guys,
>>>
>>> Has some default changed between 9.1-RC2 and HEAD?
>>>
>
Hi.
This patch takes callout(9) and redesign the KPI and the
implementation. The main objective of this work is making the
subsystem tickless. In the last several years, this possibility has
been discussed widely (http://markmail.org/message/q3xmr2ttlzpqkmae),
but until now noone really implemente
On Fri, Dec 14, 2012 at 7:41 AM, Luigi Rizzo wrote:
>
> On Fri, Dec 14, 2012 at 12:12 AM, Davide Italiano
> wrote:
>>
>> Hi.
>> This patch takes callout(9) and redesign the KPI and the
>> implementation. The main objective of this work is making the
>> s
On Fri, Dec 14, 2012 at 1:57 PM, Davide Italiano wrote:
> On Fri, Dec 14, 2012 at 7:41 AM, Luigi Rizzo wrote:
>>
>> On Fri, Dec 14, 2012 at 12:12 AM, Davide Italiano
>> wrote:
>>>
>>> Hi.
>>> This patch takes callout(9) and redesign the KPI and th
e typos.
The costant is /* 18446744073709 = int(2^64 / 100) */ used to
convert from timeval to bintime.
> On 12/14/12, Davide Italiano wrote:
>> On Fri, Dec 14, 2012 at 1:57 PM, Davide Italiano
>> wrote:
>>> On Fri, Dec 14, 2012 at 7:41 AM, Luigi Rizzo wrote:
>>>
On Sat, Dec 15, 2012 at 10:05 AM, Adrian Chadd wrote:
> Hi,
>
> Can you please test with MIPS? David has a MIPS board now.
>
Quoting from my first mail -- "We tested the code on amd64, MIPS and arm."
I used the board you gave to me. I run only some "basic" tests, but I
can look forward running so
On Sat, Dec 15, 2012 at 12:34 PM, Mark Johnston wrote:
> On Sat, Dec 15, 2012 at 06:55:53PM +0200, Alexander Motin wrote:
>> Hi.
>>
>> I'm sorry to interrupt review, but as usual good ideas came during the
>> final testing, causing another round. :) Here is updated patch for
>> HEAD, that include
On Mon, Dec 17, 2012 at 11:27 AM, Luigi Rizzo wrote:
> [addressing the various items separately]
>
> On Fri, Dec 14, 2012 at 01:57:36PM +0100, Davide Italiano wrote:
>> On Fri, Dec 14, 2012 at 7:41 AM, Luigi Rizzo wrote:
> ...
>> > - for several functions the on
On Mon, Dec 17, 2012 at 2:39 PM, David O'Brien wrote:
> On Sat, Dec 15, 2012 at 11:13:26PM +0200, Alexander Motin wrote:
>> On 15.12.2012 23:03, Alexander Motin wrote:
>> > Sorry, it's my fault. I've tried to save some time on patch generation
>> > and forgot about that change in lib/. We haven't
On Wed, Dec 19, 2012 at 1:54 AM, Poul-Henning Kamp wrote:
>
> In message <1355873265.1198.183.ca...@revolution.hippie.lan>, Ian Lepore
> writes
> :
>>On Tue, 2012-12-18 at 23:58 +0100, Luigi Rizzo wrote:
>
>>I'm not so sure about the 2^k precision. You speak of seconds, but I
>>would be
On Wed, Dec 19, 2012 at 4:18 AM, Bruce Evans wrote:
> On Wed, 19 Dec 2012, Poul-Henning Kamp wrote:
>
>>
>> In message
>>
>> , Davide Italiano writes:
>>
>>> Right now -- the precision is specified in 'bintime', which is a bin
dropping phk _AT_ onelab2 _DOT_ something from CC as long as it
doesn't seem a valid mail address and I'm annoyed mails bounce back.
On Wed, Dec 19, 2012 at 6:20 AM, Bruce Evans wrote:
> On Wed, 19 Dec 2012, Davide Italiano wrote:
>
>> On Wed, Dec 19, 2012 at 4:18
On Sun, Dec 30, 2012 at 10:17 PM, Luigi Rizzo wrote:
> On Sun, Dec 30, 2012 at 04:13:43PM -0700, Ian Lepore wrote:
> ...
>> I grabbed testsleep.c to test an arm event timer implementation, and had
>> to fix a couple nits... kqueueto was missing from the names[] array, and
>> I had to add a "* 1000
On Sat, Jan 26, 2013 at 1:58 AM, hiren panchasara
wrote:
> I've tried to update hwpmc by adding support for xeon class of Ivy
> bridge processors.
>
> Thanks Jim for pointing me to the correct document. (325462-045US Jan 2013)
>
> I do not have a reference machine to test with. Any help in that
>
On Tue, Jan 29, 2013 at 12:29 AM, hiren panchasara
wrote:
> On Mon, Jan 28, 2013 at 7:27 PM, hiren panchasara
> wrote:
>> On Sat, Jan 26, 2013 at 1:58 AM, hiren panchasara
>> wrote:
>>> I've tried to update hwpmc by adding support for xeon class of Ivy
>>> bridge processors.
>>>
>>> Thanks Jim f
On Fri, Feb 1, 2013 at 2:17 AM, hiren panchasara
wrote:
> Hi,
>
> I've prepared a patch to add core and uncore events support for
> haswell processor.
> I do not have the hardware to test this. It applies cleanly and
> compiles fine though.
>
> http://www.strugglingcoder.info/patches/hwpmc_hw.txt
[trimmed old mails]
Here's a new version of the patch:
http://people.freebsd.org/~davide/patches/calloutng-11022012.diff
Significant bits changed (after wider discussion and suggestion by phk@):
- Introduction of the new sbintime_t type (32.32 fixed point) with the
respective conversion (sbintime
On Sun, Feb 17, 2013 at 2:58 AM, hiren panchasara
wrote:
> With revision=246484, it seems we have hit the limit.
> At $WORK we have one more flag and to accommodate that we need to bump this
> up.
>
> Can p_flag be bumped up to u_long?
>
> Index: proc.h
> =
On Tue, Feb 19, 2013 at 3:22 PM, Simon L. B. Nielsen wrote:
> Hey,
>
> I think r246916 broke the build. I get the following when building amd64
> kernel:
>
> cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g
> -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
> -Wmis
On Wed, Feb 20, 2013 at 10:54 AM, Dag-Erling Smørgrav wrote:
> Davide Italiano writes:
>> Unfortunately tinderbox didn't catch this bug because it's triggered
>> only when gcc is used to build kernel.
>
> In this particular case, the broken code is only built
The patch has been splitted in smaller logical chunks in order to
improve readability and facilitate review.
The whole code can be found here:
http://people.freebsd.org/~davide/calloutng_split/
In particular:
http://people.freebsd.org/~davide/calloutng_split/sbintime.diff brings
the new type 32.32
On Wed, Aug 1, 2012 at 7:05 PM, Arnaud Lacombe wrote:
> Hi,
>
> On Wed, Aug 1, 2012 at 12:40 PM, Attilio Rao wrote:
>> On Wed, Aug 1, 2012 at 5:32 PM, Arnaud Lacombe wrote:
>>> Hi,
>>>
>>> On Tue, Jul 31, 2012 at 4:14 PM, Attilio Rao wrote:
You don't want to work cooperatively.
>
On Fri, Sep 6, 2013 at 6:00 PM, Sean Bruno wrote:
> Our "yBSD" builder needs to mount a disk image temporarily that has a
> dos partition (for openstack-ish things) to put configs into it. It
> seems that under high stress, we can squeeze a panic out of it in
> namei().
>
> Sean
>
>
> Unread port
On Sun, Sep 8, 2013 at 4:27 PM, Sean Bruno wrote:
> On Sat, 2013-09-07 at 17:05 +0200, Davide Italiano wrote:
>> On Fri, Sep 6, 2013 at 6:00 PM, Sean Bruno wrote:
>> > Our "yBSD" builder needs to mount a disk image temporarily that has a
>> > dos partit
>
> Thanks Gleb.
> I've removed DIAGNOSTIC and the problem is gone now.
>
JFYI, I hit this problem today as well. I don't think you really need
to disable DIAGNOSTIC completely in order to get rid of that.
I've noticed Peter Holm has recently committed a new sysctl that
allows you to selectively d
On Sat, Sep 21, 2013 at 2:51 PM, O. Hartmann
wrote:
> On Sat, 21 Sep 2013 07:08:25 -0500
> Bryan Drewery wrote:
>
>> On 9/21/2013 7:06 AM, Bjoern A. Zeeb wrote:
>> > On Sat, 21 Sep 2013, Bryan Drewery wrote:
>> >
>> >>> Unread portion of the kernel message buffer:
>> >>> panic: Lock lle not exclu
On Sat, Sep 21, 2013 at 9:31 AM, Bryan Drewery wrote:
> On 9/21/2013 11:18 AM, Adam McDougall wrote:
>> On 09/21/13 09:41, Davide Italiano wrote:
>>> On Sat, Sep 21, 2013 at 2:51 PM, O. Hartmann
>>> wrote:
>>>> On Sat, 21 Sep 2013 07:08:25 -0500
>>>
On Sun, Sep 22, 2013 at 2:25 AM, Lars Engels wrote:
> On Sat, Sep 21, 2013 at 11:23:47PM -0700, Tim Kientzle wrote:
>> I'm seeing this panic pretty consistently when I try to do a buildworld on
>> r255764 (i386):
>>
>> http://people.freebsd.org/~kientzle/r255764%20panic%202013-09-21%20at%209.27.0
On Sun, Sep 22, 2013 at 2:28 PM, Lars Engels wrote:
> On Sun, Sep 22, 2013 at 05:11:30AM -0700, Davide Italiano wrote:
>> On Sun, Sep 22, 2013 at 2:25 AM, Lars Engels wrote:
>> > On Sat, Sep 21, 2013 at 11:23:47PM -0700, Tim Kientzle wrote:
>> >> I'm seeing th
On Sun, Sep 22, 2013 at 1:40 PM, Miguel Clara wrote:
> Its definatly not related to GCC, I'm getting the same while trying to
> "buildkernel", I'm trying to upgrade to a more recent current version! Same
> kernel panic is showing...
>
> No one else had this problem yet?
>
> Thanks
>
>
> On Sun, Se
On Sun, Sep 22, 2013 at 1:47 PM, Miguel C. wrote:
> Hum, its probably best to take a scrennshot since I can't copy this from
> the console!
>
> attaching the file
>
That was a regression I introduced, but I'm confident r255788 fixed
the issue. Please update your sources and rebuild your kernel.
On Sun, Sep 22, 2013 at 2:06 PM, Miguel Clara wrote:
> I sent the mail again to the list in a smaller size, the first one was
> huge ...
>
> Anyway that's the revision I'm trying to build --> r255788 ... but the
> problem is, I can't buildkernel, I get a panic while doing it... so unless
> there's
On Sun, Sep 22, 2013 at 2:47 PM, Miguel Clara wrote:
> Thanks for the suggestion but I would have tried it If r255788 or newer was
> there but its not the case!
>
> I also checked
> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/amd64/10.0-CURRENT/ but
> kernel.txz seems to be "outdated"
On Wed, Sep 25, 2013 at 11:11 AM, Anton Shterenlikht wrote:
> FreeBSD mech-as221.men.bris.ac.uk 10.0-ALPHA2 FreeBSD 10.0-ALPHA2 #8 r255811:
> Tue Sep 24 09:04:17 BST 2013
> r...@mech-as221.men.bris.ac.uk:/usr/obj/usr/src/sys/UZI ia64
>
> panic: deadlkres: possible deadlock detected for 0xe0
On Wed, Sep 25, 2013 at 5:30 PM, Anton Shterenlikht wrote:
> >From davide.itali...@gmail.com Wed Sep 25 16:12:47 2013
>>
>>Can you please paste the output of 'show locks', 'show alllocks',
>>'show lockedvnods' at least?
>>Ideally you should provide all the informations listed here.
>>http://www.fr
On Thu, Sep 26, 2013 at 12:23 PM, Anton Shterenlikht wrote:
>
> Regarding textdump(4), I'm not clear where the following
> "scripts" should be located and used:
>
[snip]
> Are these ddb(8) commands? Or do I set these in /etc/rc.conf?
>
The scripts (quotes unneeded) should be located in /etc/ddb
On Tue, Oct 1, 2013 at 9:05 AM, Alexander Yerenkow wrote:
> Hello all.
> Can someone help me? :)
[trim]
>
> ===> usr.bin/clang/tblgen (obj,depend,all,install)
> ...
> c++ -O2 -pipe
> -I/zbuilder/vm4all/src-stable-9-clone/usr.bin/clang/tblgen/../../../contrib/llvm/include
> -I/zbuilder/vm4all/src
On Fri, Oct 11, 2013 at 11:26 AM, Anton Shterenlikht wrote:
> >From davide.itali...@gmail.com Thu Sep 26 13:12:30 2013
>>On Thu, Sep 26, 2013 at 12:23 PM, Anton Shterenlikht wrote:
>>>
>>> Regarding textdump(4), I'm not clear where the following
>>> "scripts" should be located and used:
>>>
>>
>>
On Mon, Oct 14, 2013 at 10:21 AM, Anton Shterenlikht wrote:
> >From davide.itali...@gmail.com Fri Oct 11 15:39:49 2013
>>
>>If you're not able to get a full dump, a textdump would be enough.
>>In your DDB scripts just remove the 'call doadump' step and you should
>>be done, unless I'm missing some
On Tue, Oct 15, 2013 at 10:43 AM, Anton Shterenlikht wrote:
> Anyway, savecore eventually deadlocks:
>
> panic: deadlkres: possible deadlock detected for 0xe000127b7b00, blocked
> for 901401 ticks
>
[trim]
>
> Tracing command savecore pid 805 tid 100079 td 0xe000127b7b00
> cpu_switch(0
On Tue, Oct 15, 2013 at 4:17 PM, Anton Shterenlikht wrote:
> I'm trying to set up textdump(4).
>
> On boot I see:
>
> WITNESS: unable to allocate a new witness object
>
> also
It means that you run out of WITNESS object on the free list.
>
> Expensive timeout(9) function: 0x9ffc00e222e0(0xa0
One of my personal goals for 11 is to get rid of cloning mechanism
entirely, and pty(4) is one of the few in-kernel drivers still relying
on such mechanism.
It's not possible, at least to my understanding, converting pty(4) to
cdevpriv(9) as happened with other drivers. This is mainly because we
al
r258695 introduces a sanity check for makefs in order to verify that
minimum image size specified is always less than maximum image size.
If makefs(1) is invoked specifying minimum image size, but not maximum
one, the program exits with an error. Example:
# sudo -E makefs -M 538968064 -B be /home
On Wed, Mar 27, 2013 at 9:28 PM, Pawel Pekala wrote:
> For some time now (about month?) ports using sys/time.h include fail to
> build and I`m sure they were building ok before. At least those seems
> affected by this:
>
> math/atlas
> math/openblas
> x11-toolkits/c++-gtk-utils
>
> All fail with s
On Thu, May 2, 2013 at 8:43 AM, Andrey Chernov wrote:
> cc1: warnings being treated as errors
> /usr/src/sys/modules/hwpmc/../../dev/hwpmc/hwpmc_core.c: In function
> 'iap_allocate_pmc':
> /usr/src/sys/modules/hwpmc/../../dev/hwpmc/hwpmc_core.c:1935: warning: 'map'
> may be used uninitialized in
On Thu, May 2, 2013 at 3:10 PM, Dimitry Andric wrote:
> On 2013-05-02 12:06, Davide Italiano wrote:
>>
>> On Thu, May 2, 2013 at 8:43 AM, Andrey Chernov wrote:
>>>
>>> cc1: warnings being treated as errors
>>> /usr/src/sys/modules/hwpmc
On Thu, May 2, 2013 at 3:42 PM, Andrey Chernov wrote:
> On 02.05.2013 14:06, Davide Italiano wrote:
>>> /usr/src/sys/modules/hwpmc/../../dev/hwpmc/hwpmc_core.c:1935: warning:
>>> 'map' may be used uninitialized in this function
>>> *** [hwpmc_core.o
On Mon, Aug 5, 2013 at 4:24 PM, Sam Fourman Jr. wrote:
> I am going to respond to this before I forget
>
> I had the SAME exact LOR's with ath 9300 and I reported them,
> however I have since switched out motherboards and the LOR's have strangely
> diapered
>
>
> here is a full dmesg for a per
On Sun, Aug 11, 2013 at 9:20 AM, Larry Rosenman wrote:
> In the last 12 hours I've had 4 crashes related to ZFS.
>
>
> total 97
> -rw-r--r-- 1 ler ler 136488 Aug 11 11:17 core.txt.1
> -rw-r--r-- 1 ler ler 117213 Aug 11 11:17 core.txt.2
> -rw-r--r-- 1 ler ler 120357 Aug 11 11:17 core.txt.3
On Mon, Aug 12, 2013 at 8:13 AM, David Wolfskill wrote:
> I first noticed this on my laptop on 08 Aug, after having built & booted
>
> FreeBSD 10.0-CURRENT #975 r253985M/253985:141: Tue Aug 6 05:28:39 PDT
> 2013 root@localhost:/common/S4/obj/usr/src/sys/CANARY i386
>
> OK. I'm away fr
On Mon, Aug 12, 2013 at 9:01 AM, David Wolfskill wrote:
> On Mon, Aug 12, 2013 at 08:30:15AM -0700, Davide Italiano wrote:
>> ...
>> > Booting...
>> > GDB: no debug ports present
>> > KDB: debugger backends: ddb
>> > KDB: current backend: ddb
>
On Wed, Aug 14, 2013 at 10:58 PM, Adrian Chadd wrote:
> Hi,
>
> This (and maybe more?) events are applicable to both the sandy bridge and
> sandy bridge xeon CPUs.
>
> This is from the Intel SDM June 2013 Volume #3.
>
> David/Jim, does this look fine to you?
>
> Thanks,
>
>
> ndex: sys/dev/hwpmc/h
On Fri, Aug 23, 2013 at 3:45 PM, John Baldwin wrote:
> On Friday, August 23, 2013 2:27:58 am Vitja Makarov wrote:
>> 2013/8/22 John Baldwin :
>> > On Thursday, August 22, 2013 12:18:48 am Vitja Makarov wrote:
>> >> 2013/8/21 John Baldwin :
>> >> > On Monday, August 19, 2013 11:13:02 pm Daniel Eisc
On Fri, Aug 23, 2013 at 5:29 PM, John Baldwin wrote:
> On Friday, August 23, 2013 9:53:12 am Davide Italiano wrote:
>> On Fri, Aug 23, 2013 at 3:45 PM, John Baldwin wrote:
>> > On Friday, August 23, 2013 2:27:58 am Vitja Makarov wrote:
>> >> 2013/8/22 John Baldwin
On Fri, Aug 23, 2013 at 7:04 AM, Vitja Makarov wrote:
> 2013/8/23 Davide Italiano :
>
> I think that for socket's timeouts it's ok to have a HZ-precision. It
> would be much more important to implement high-precision timeouts for
> select() and friends, if it's not d
On Sat, Aug 24, 2013 at 7:16 AM, Robert Watson wrote:
> On Sat, 24 Aug 2013, Alexander V. Chernikov wrote:
>
>> On 24.08.2013 00:54, Adrian Chadd wrote:
>>>
>>>
>>> I'd like to commit this to -10. It migrates the if_lagg locking
>>> from a rw lock to a rm lock. We see a bit of contention between t
On Thu, Aug 29, 2013 at 6:03 PM, John Baldwin wrote:
> On Monday, August 26, 2013 3:05:06 pm John Baldwin wrote:
>> On Monday, August 26, 2013 2:23:44 pm Davide Italiano wrote:
>> > Please consider the following patch:
>> > http://people.freebsd.org/~davide/review/so
On Tue, Aug 27, 2013 at 7:10 AM, Vitja Makarov wrote:
>> On Fri, Aug 23, 2013 at 7:04 AM, Vitja Makarov
>> wrote:
>>> 2013/8/23 Davide Italiano :
>>>
>>> I think that for socket's timeouts it's ok to have a HZ-precision. It
>>> would b
79 matches
Mail list logo
