From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from out-170.mta1.migadu.com (out-170.mta1.migadu.com [95.215.58.170])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3936E6A003
	for <bpf@vger.kernel.org>; Fri,  3 May 2024 04:58:36 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.170
ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116;
	t=1714712318; cv=none; b=sDa16SlejhfhDZNaENL6GV7fTpjSHHTNxgBhoMAo+zQMknRefjwXNTkwiPQyWgHw3hBo5g5XsNs714xi4y4tYFEGlw5bt6zDA2I+XmnYIXwTCzfLFaGzWr3AcMEuVjVkb16nV06aaGH8xF90cn3cI9yv7j02rwqefBUeq6ENZUg=
ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org;
	s=arc-20240116; t=1714712318; c=relaxed/simple;
	bh=vX8U81SGyZLTf6DmB6pO37KtOE3pRmrsqyCCK9koaGk=;
	h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From:
	 In-Reply-To:Content-Type; b=DgCzYEQvqUme0VB5bY1rVN8fBLo2kXHmzpoNlLmldUADoqlsOrltXCZ/YY39FPJUUBjeGeTdsfu53F0zDCu6lbg1wJaYo07UR+wGLaf+ystG/WAoP9ouYTKdO0ng56SczlpNvaIRdjQTZ+cIDktDXoMhGnT9AsYLnsm7iwDFzOo=
ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=wfHzD/nh; arc=none smtp.client-ip=95.215.58.170
Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev
Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev
Authentication-Results: smtp.subspace.kernel.org;
	dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="wfHzD/nh"
Message-ID: <dbc79eaa-7ecb-4573-be4d-e246ae44cbfb@linux.dev>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1;
	t=1714712315;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=glGTHOVMp9otLDWWtuPdMzwCHdBRiMK4Y1FYptqG85w=;
	b=wfHzD/nhT/3pX+m955I0R9JikuTqWr7W+mVNjJvygDeIIfZb1uqRvXgJ1C1zhrQV3tqEjg
	ANmtdTwx64IcsRX6AZ8yrSi16vR9hLq8b7r/vmb7iiQl+CAaF0MU3aqx+20vuSmuiQ0+wR
	joCnslxIApB6R4mcz+jbNRWz4mxN9k8=
Date: Thu, 2 May 2024 21:58:27 -0700
Precedence: bulk
X-Mailing-List: bpf@vger.kernel.org
List-Id: <bpf.vger.kernel.org>
List-Subscribe: <mailto:bpf+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:bpf+unsubscribe@vger.kernel.org>
MIME-Version: 1.0
Subject: Re: [PATCH bpf-next] bpf: fix bpf_ksym_exists in GCC
Content-Language: en-GB
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <alexei.starovoitov@gmail.com>,
 david.faust@oracle.com, cupertino.miranda@oracle.com
References: <20240428112559.10518-1-jose.marchesi@oracle.com>
 <c4d99195-f000-47f2-b167-12e76b705dc9@linux.dev> <874jbgqdhd.fsf@oracle.com>
X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers.
From: Yonghong Song <yonghong.song@linux.dev>
In-Reply-To: <874jbgqdhd.fsf@oracle.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Migadu-Flow: FLOW_OUT


On 5/2/24 11:23 AM, Jose E. Marchesi wrote:
>>          .long   runqueues
>>          .long   3264
>>          .long   388
> Just to be sure, there seems to be a little discrepancy.  The size of
> runqueues (struct rq) in the latest bpf-next is 3456 instead of 3264,
> when compiled by both clang 18 and GCC.  This is correctly reflected in
> the BTF generated by both compilers.
>
> Is the size of struct rq different in your testing machine?

Probably due to different configrations. Anyway, libbpf/kernel will do proper
rewrite to reference to the proper kernel runqueus.