Re: Kernel traces

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Kernel traces
From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
Date: Tue, 11 Dec 2018 23:16:17 -0700
Cc: Btrfs BTRFS <linux-btrfs@xxxxxxxxxxxxxxx>
In-reply-to: <20181211115226.GA20157@cuci.nl>
References: <20181210120514.GA14828@cuci.nl> <CAJCQCtQxaAKMP9qSF1UnOG7cy8ya=4MckGt9kL0O8oGxD4fitg@mail.gmail.com> <20181211115226.GA20157@cuci.nl>

Also, what scheduler are you using? And do you get different results
with a different one (better or worse)?


Chris Murphy

Follow-Ups:
- Re: Kernel traces
  - From: Stephen R. van den Berg

References:
- Kernel traces
  - From: Stephen R. van den Berg
- Re: Kernel traces
  - From: Chris Murphy
- Re: Kernel traces
  - From: Stephen R. van den Berg

Prev by Date: Re: [PATCH 3/8] btrfs: delayed-ref: Use btrfs_ref to refactor btrfs_add_delayed_tree_ref()
Next by Date: Re: Kernel traces
Previous by thread: Re: Kernel traces
Next by thread: Re: Kernel traces
Index(es):
- Date
- Thread

[Index of Archives] [Linux Filesystem Development] [Linux NFS] [Linux NILFS] [Linux USB Devel] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI]

Powered by Linux