On Sun, Sep 22, 2024 at 6:25 AM Vlastimil Babka wrote:
>
> On 9/21/24 23:08, Guenter Roeck wrote:
> > On 9/21/24 13:40, Vlastimil Babka wrote:
> >> +CC kunit folks
> >>
> >> On 9/20/24 15:35, Guenter Roeck wrote:
> >>> Hi,
> >>
> >> Hi,
> >>
> >>> On Wed, Aug 07, 2024 at 12:31:20PM +0200, Vlastimi
://download.01.org/0day-ci/archive/20240921/202409212201.l94ghfkw-...@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot
| Closes: https://lore.kernel.org/r
Hi all,
On 9/3/24 18:36, Diego Vieira wrote:
Hi all,
This is part of a hackathon organized by LKCAMP [1], focused on writing
tests using KUnit. We reached out a while ago asking for advice on what would
be a useful contribution [2] and ended up choosing data structures that did
not yet have tes
On 9/21/24 23:08, Guenter Roeck wrote:
> On 9/21/24 13:40, Vlastimil Babka wrote:
>> +CC kunit folks
>>
>> On 9/20/24 15:35, Guenter Roeck wrote:
>>> Hi,
>>
>> Hi,
>>
>>> On Wed, Aug 07, 2024 at 12:31:20PM +0200, Vlastimil Babka wrote:
Add a test that will create cache, allocate one object,
> +/*
> + * hpref_hp_get: Obtain a reference to a stable object, protected either
> + * by hazard pointer (fast-path) or using reference
> + * counter as fall-back.
> + */
> +static inline
> +bool hpref_hp_get(struct hpref_node **node_p, struct hpref_ctx *ctx)
> +{
> +
On 9/21/24 13:40, Vlastimil Babka wrote:
+CC kunit folks
On 9/20/24 15:35, Guenter Roeck wrote:
Hi,
Hi,
On Wed, Aug 07, 2024 at 12:31:20PM +0200, Vlastimil Babka wrote:
Add a test that will create cache, allocate one object, kfree_rcu() it
and attempt to destroy it. As long as the usage of
+CC kunit folks
On 9/20/24 15:35, Guenter Roeck wrote:
> Hi,
Hi,
> On Wed, Aug 07, 2024 at 12:31:20PM +0200, Vlastimil Babka wrote:
>> Add a test that will create cache, allocate one object, kfree_rcu() it
>> and attempt to destroy it. As long as the usage of kvfree_rcu_barrier()
>> in kmem_cach
On 20/09/2024 18:38, Abdellatif El Khlifi wrote:
> Hi Krzysztof,
>
> + '#extsys-id':
'#' is not correct for sure, that's not a cell specifier.
But anyway, we do not accept in general instance IDs.
>>>
>>> I'm happy to replace the instance ID wit
Boqun Feng's patch series and LPC talk gave me a few ideas I wanted to
try. I figured we could improve the concept of reference counters by
adding a hazard-pointer protected fast-path to them.
This API combines hazard pointers and reference counters.
It uses hazard pointers as fast-paths, and fall
Tiago Lam wrote:
> This follows the same rationale provided for the ipv4 counterpart, where
> the sendmsg() path is also extended here to support the IPV6_ORIGDSTADDR
> ancillary message to be able to specify a source address/port. This
> allows users to configure the source address and/or port egr
Tiago Lam wrote:
> sendmsg() doesn't currently allow users to set the src port from which
> egress traffic should be sent from. This is possible if a user wants to
> configure the src address from which egress traffic should be sent from
> - with the IP_PKTINFO ancillary message, a user is currentl
11 matches
Mail list logo
