netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: allison.henderson@oracle.com, netdev@vger.kernel.org,
	linux-rdma@vger.kernel.org, rds-devel@oss.oracle.com
Subject: Re: [PATCH RFC v1] rds: Expose feature parameters via sysfs and ELF note
Date: Thu, 12 Jun 2025 12:17:05 +0300	[thread overview]
Message-ID: <20250612091705.GU10669@unreal> (raw)
In-Reply-To: <20250610191144.422161-2-konrad.wilk@oracle.com>

On Tue, Jun 10, 2025 at 12:27:25PM -0400, Konrad Rzeszutek Wilk wrote:
> We would like to have a programatic way for applications
> to query which of the features defined in include/uapi/linux/rds.h
> are actually implemented by the kernel.

If you are interested in programmatic way, the IOCTL/netlink/syscall/...
are the right approach for it and not sysfs files.

Why don't you follow standard way of doing it by creating new query IOCTL
command? Which will return declared feature bitmask, which application can
parse and understand?

Thanks

  parent reply	other threads:[~2025-06-12  9:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10 16:27 [PATCH RFC v1] Feature reporting of RDS driver Konrad Rzeszutek Wilk
2025-06-10 16:27 ` [PATCH RFC v1] rds: Expose feature parameters via sysfs and ELF note Konrad Rzeszutek Wilk
2025-06-10 20:30   ` Andrew Lunn
2025-06-10 20:41     ` Konrad Rzeszutek Wilk
2025-06-10 20:50       ` Andrew Lunn
2025-06-10 20:54         ` Konrad Rzeszutek Wilk
2025-06-10 20:51   ` Konrad Rzeszutek Wilk
2025-06-12  9:17   ` Leon Romanovsky [this message]
2025-06-10 20:47 ` [rds-devel] [PATCH RFC v1] Feature reporting of RDS driver Konrad Rzeszutek Wilk
2025-06-10 21:32   ` Tejun Heo
2025-06-10 23:15     ` Konrad Rzeszutek Wilk
2025-06-16 17:45       ` Tejun Heo
2025-06-10 21:09 ` Allison Henderson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250612091705.GU10669@unreal \
    --to=leon@kernel.org \
    --cc=allison.henderson@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rds-devel@oss.oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).