based on `struct hlist_head`
Needs ReviewPublic
Actions

Authored by dumbbell on Mon, Aug 10, 5:33 PM.

Tags

Referenced Files

	F171043687: D58765.diff
	Tue, Sep 8, 9:04 AM

	Unknown Object (File)
	Sat, Sep 5, 1:49 AM

	Unknown Object (File)
	Fri, Sep 4, 11:05 PM

	Unknown Object (File)
	Thu, Sep 3, 8:00 PM

	Unknown Object (File)
	Thu, Sep 3, 2:09 AM

	Unknown Object (File)
	Tue, Sep 1, 4:10 PM

	Unknown Object (File)
	Tue, Sep 1, 1:58 AM

	Unknown Object (File)
	Mon, Aug 31, 3:47 AM

View All 37 Files

Subscribers

emaste

imp

Details

Reviewers

None

Group Reviewers

linuxkpi

Summary

This is the case on Linux.

The admgpu DRM driver started to use the hlist API directly to move entries from one hashtable to another one in Linux 6.15.

Diff Detail

Lint

Lint Skipped

Unit

Tests Skipped

Event Timeline

dumbbell created this revision.Mon, Aug 10, 5:33 PM

Herald added subscribers: emaste, imp. · View Herald TranscriptMon, Aug 10, 5:33 PM

dumbbell requested review of this revision.Mon, Aug 10, 5:33 PM

dumbbell added a parent revision: D58764: linuxkpi: Add `shmem_read_folio()`.

Seems like the right thing to do. Does linux hlist have any concurrency support?

emaste added a project: linuxkpi.Mon, Aug 17, 4:57 PM

In D58765#1349262, @emaste wrote:

Seems like the right thing to do. Does linux hlist have any concurrency support?

No, there is no locking or other concurrent-related mechanism used by this API.

Revision Contents
Changeset List

Path

Size

sys/

compat/

linuxkpi/

common/

include/

linux/

hashtable.h

76 lines

Diff 183800

View Options

sys/compat/linuxkpi/common/include/linux/hashtable.h

linuxkpi: Re-implement <linux/hashtable.h> based on `struct hlist_head`Needs ReviewPublicActions